Peter Dalgaard
A couple of things in the applications area do show that we're dealing with a "raw port" of the 32 bit version. I have noticed that texmacs and OpenOffice have issues in this version. Texmacs is just not 64 bit clean at this stage and something of a fringe application so it's probably a bit harsh on the SuSE guys to expect them to fix it. On the other hand, you might have expected them at least to note that it segfaults immediately on start...
Please send me details and I create a bugreport...
The issues with OOo take a bit more testing to find, but I can generally crash it within 5 minutes of playing with the formula editor (and given all the other things I have thrown at that box, I think hardware failure is not the likely reason). Unlike texmacs, OOo is a central piece of software for those who want a 64bit desktop, so this could be said to deserve a more dedicated effort to get rid of such bugs.
OOo is a 32-bit application. It uses so much architecture dependend code that you cannot just recompile it, you need to port a lot of stuff. OOo 2.0 is supposed to run on AMD64, let's see... So, your OOo problems should occur on x86 also.
I consider the support provided by Mr. Kleen and Mr. Jaeger in this forum to be very good.
Yup. I can't help getting the feeling that they are pretty much alone on the task, though. There's not a large "back room" full of people fixing bugs or pushing reports to upstreams maintainers.
But there are some that I can throw good bugreports at ;-) Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SUSE Linux AG, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126