Apache OpenOffice (AOO) Bugzilla – Issue 16223
setup segfault, older versions crash as well
Last modified: 2003-09-08 16:53:51 UTC
first of all thank you again for your fine work! my problem: i worked with ooo (different versions) very sufficiently. from one day to another (just after installing 1.1beta2 and runnig it for testing purposes), no single applicatin belonging to ooo seeed to start any longer. i installed the beta in a new directory, but now can't run any setup any more, despite ooo's version. every ooo-application crashes with a segfault (while i didn't recognize any other program to cause problems). so, i cannot even run the 'repair' process to get the former working 1.0.3.1 back again, and have no idea why... my web-searches over the past few days brought no solution (just some glimpse that it might have something to do with the fonts - libfreetype6 maybe?). even the official debian-package doesn't start its setup. apart from the "segfault"- and one "uname"-message, ooo gives no errors when ran from console - it just quits. can you help me? my system: athlon 1200, matrox mga g200 (tried the fix from the readme, didn't change anything), debian testing/unstable, kde 3.1.2, kernel 2.4.21, xfree4.3.0-0ds4
Am I right: OOo has been running but won't start any more? You haven't changed anything on your system? Which glibc do you have on your system? If you have 2.3.1 upgrade to 2.3.2 or downgrade to 2.2.5. 2.3.1 is buggy.
thanks for your fast reply. you were right (s.o.). well, i switched from 2.3.1 to 2.3.2 - but it didn't change anything :-( this is odd, isn't it?
Have you reinstalled your OOo versions after upgrading your system? On RH9 and Suse 8.2, both with glibc2.3.2, I can't reproduce. OOo is starting and running fine.
the thing is, i _can't_ reinstall... that's what bothers me. setup seems to start as usual (it opens that small window with a blue box and progress bar, obviously it's unpacking temp-files or so), and then about 2 seconds later (window's gone) i find myself back on the konsole prompt. before it stops, it writes "glibc version: 2.3.2" followed by "see »uname --help« for further information" or so, that's all. no additional error messages or anything else.
I have no idea. Maybe the glibc ist still buggy?? Do you have correct rights on your system after updating? Is a sv00x.tmp folder created by setup? Try setup -dontdeletetemp to create such a temporary folder. Open this folder and start setup frum this folder.
first of all, thank you again for your efforts to help me... i tried to run the setup from within the temp-folder and still run ito a segfault message. i don't recall changing any essetials of my system lately (apart from the glibc update you recommended), so i don't think it's to do with wrong permissions (i've tried as user and root from various folders). is it possible that there's a problem with the gcc-version the libraries are compiled with? sarge (debian unstable) is merging to gcc-3, and i had trouble with compiling apps for kde in the past (must compile with 2.95, because 3.2 doesn't work with the qt3-libs in 'stable'; i assume my glibc was compiled with gcc-3.2 as well - would it help to recompile ooo myself?). is there a way to dump setup error messages somehow?
I think that recompiling OO would help. I've been told that OOo would also run if you compile it with glibc 2.3.1 on your machine. So I think you should do this for glibc 2.3.2 also. I don't know a way to dump error messages. Good luck :-)
I think the transition to a newer gcc Debian testing/unstable is going through is indeed a likely cause of your trouble. Until that transition is complete, users are likely to have trouble running OpenOffice.org there. I'm going to close this as 'invalid' for the moment since it's most likely a problem on Debian's end rather than an OpenOffice problem. If you can reproduce this on debian/stable, with no testing or unstable libraries, please reopen the issue. FWIW, when trying to debug crashes like this, it helps to run the crashing program under gdb; that lets you get a stack dump. You may have to edit the program's wrapper shell script to do this. See http://kegel.com/openoffice
finally, i found out what went wrong a few minutes ago: it was a true type font (americana bt)! after weeks of trying almost everything (compile didn't work, btw...), i tested the packages from http://openoffice.debian.net. guess what, they crashed as well, but their README.Debian comes with some very useful hints to perform a bug-hunt in cases like mine. the following did the trick to find the corrupted font (cd into oo's "program" directory first) (LD_LIBRARY_PATH=. strace ./setup.bin 2>&1) | grep open | grep .ttf | tail what a relief ;-)