OOo writer (2.4.1) crashes - A LOT

[wallsp8]

Suddenly OOo writer has started crashing - VERY REGULARLY. I'm running OOo 2.4.1 with writer's tools on SuSE 9.2. I haven't had this problem up until today. No problems with previous versions of OOo. Using v2.2 on Ubuntu with no issues. The document in question is MS word format, but others have also crashed (for testing purposes).

Has anyone else had this issue? I'd really like to get past it soon!

[acknak]

Try renaming or removing your OOo user settings.

[wallsp8]

Ouch, not good. Now it crashes as soon as I start it and tries to recover a blank document. I'd really like to avoid re-installing, if I can. Any other suggestions?

[TheGurkha]

Is this the official sun build or the distro version? I'd go Sun version everytime.

[acknak]

Ugh. Sorry.

I don't know what else to suggest. Have you updated any components of your system lately?

The most common cause of sudden bouts of instability is corrupted settings.

You could also try running OOo while logged in from a new user account--in case something else in your home directory or settings is causing the problem.

[wallsp8]

Official Sun Build - yes. The only system changes I have made lately are a new printer (actually haven't set it up on the Linux partition, yet). I'll try the alt user trick to see if that works. If not, maybe I can find the 2.4.0 release. Funny that I had no problems at the .0 release, but first patch is a headache. Usually it's the other way around.

[wallsp8]

Alternate user didn't do the trick. Any other suggestions are welcome.

[acknak]

The only other debugging strategy that I know of is to run OOo under strace, and the scan the output to see if any errors give you a clue why/where it's blowing up. It's a stretch, but sometimes something like wrong permissions on a file somewhere can cause a problem.

I use something like: $ strace -f -o trace.log ooffice, or if OOo is already running, $ strace -f -p 6603 -o trace.log

[AndrewZ]

I get something like this too. It started when I upgraded from Fedora 7 to 9 or from 2.4.0 to 2.4.1. When I start OOo from Nautilus, it crashes on startup. When I start OOo from gnome-terminal, it runs OK. Resetting my user profile did not help. That's all I had time to figure out so far.

I also noticed this error message on the console
Gtk-Message: Failed to load module "gnomebreakpad": /home/z/download/ooo-dev/OOO300_m2_native_packed-1_en-US.9343/RPMS/opt/ooo-dev3/program/../basis-link/ure-link/lib/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by /usr/lib/bug-buddy/libbreakpad.so.0)

[acknak]

Hmm, that's interesting.

OOo 2.4.1 runs fine for me on F9, but all the OOo 3 snapshots have triggered that error. The application starts and runs fine from a console, but running on the desktop, the error is detected and the application doesn't start.

The exact error I see is:

$ OOo_3.0.29_unxlngi6_install/ooo-dev3/program/soffice
Gtk-Message: Failed to load module "gnomebreakpad": /home/jes/tmp/OOo_3.0.29_unxlngi6_install/ooo-dev3/program/../basis-link/ure-link/lib/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by /usr/lib/bug-buddy/libbreakpad.so.0)

I doubt that the OOo people have any interest in dealing with this, as it appears (to me) to be a system integration issue: the installed bug-buddy is not compatible with the glibc used to build OOo.

I brought it up on a Fedora mailing list, but got no helpful suggestions.

[AndrewZ]

wallsp8 : how about sudo rpm -e bug-buddy? Works for me. Does it help you?

Please run the following and paste the results.

Code: Select all

rpm -qa glibc bug-buddy  libstdc++