GNOME Bugzilla – Bug 123743
Crash on startup for Gnumeric 1.2.0 on Slackware 9.1
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Slackware Slackware 9.1.0 Package: Gnumeric Severity: critical Version: GNOME2.4.0 1.1.x Gnome-Distributor: GNOME.Org Synopsis: Crash on startup for Gnumeric 1.2.0 on Slackware 9.1 Bugzilla-Product: Gnumeric Bugzilla-Component: General Bugzilla-Version: 1.1.x BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: alex@allele2:~$ gnumeric Bonobo accessibility support initialized GTK Accessibility Module initialized Atk Accessibilty bridge initialized ** ERROR **: error condition on server fd is 0 aborting... Bonobo accessibility support initialized GTK Accessibility Module initialized Atk Accessibilty bridge initialized Crashes with a dialog box with this information: Application "gnumeric" (process 9015) has crashed due to a fatal error. (Aborted) Steps to reproduce the crash: 1. Run gnumeric from the command line 2. 3. Expected Results: Gnumeric starts. How often does this happen? Sometimes after a logoff/login or a reboot it will work, but once it has failed once in a session, it won't work for that session. Clearing out the .gnome2/Gnumeric prefs doesn't seem to help. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnumeric' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 16384 (LWP 8978)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x40fbe5c9 in waitpid () from /lib/libpthread.so.0
+ Trace 40599
Thread 1 (Thread 16384 (LWP 8978))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-10-02 21:35 ------- Reassigning to the default owner of the component, jody@gnome.org.
The console messages indicate that this is an occurrence of bug 121675, but there also seems to be a similarity with 123395. *** This bug has been marked as a duplicate of 121675 ***
*** Bug 124397 has been marked as a duplicate of this bug. ***