GNOME Bugzilla – Bug 126681
Gnumeric segfaults on startup
Last modified: 2004-12-22 21:47:04 UTC
Package: Gnumeric Severity: major Version: 1.2.1 Synopsis: Gnumeric segfaults on startup Bugzilla-Product: Gnumeric Bugzilla-Component: General BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of Problem: Gnumeric segfaults while starting before any part of the GUI has been displayed. Steps to reproduce the problem: 1. Start gnumeric. Actual Results: Segfault Expected Results: Normal startup How often does this happen? Always Additional Information: This pertains to the Debian i386 unstable build of Gnumeric 1.2.1-3. 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)...(no debugging symbols found)...[New Thread 16384 (LWP 3774)] (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)...0x40e63bb8 in waitpid () from /lib/libpthread.so.0
+ Trace 41631
Thread 1 (Thread 16384 (LWP 3774))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-11-10 21:47 ------- The original reporter (ehn@kth.se) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, jody@gnome.org.
Please start from the command line and tell us what message it is pringint before it dies.
This is the output from Gnumeric before it crashes: $ 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 I realize now that it doesn't actually segfault, but crashes for some other reason. Thanks for your help! Andreas
Dupe of bug 121675.
*** This bug has been marked as a duplicate of 121675 ***