GNOME Bugzilla – Bug 157682
Crashes immediately on start
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Debian 3.1 Package: Gnumeric Severity: normal Version: GNOME2.6.1 unspecified Gnome-Distributor: Debian Synopsis: Crashes immediately on start Bugzilla-Product: Gnumeric Bugzilla-Component: General Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.6.1.1) Description: Description of the crash: Crashes directly on opening of certain gnumeric file from Nautilus How often does this happen? Every time. Debugging Information: Backtrace was generated from '/usr/bin/gnumeric' (no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1". (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)...[Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 8428)] (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)...0x408f6be8 in waitpid () from /lib/libpthread.so.0
+ Trace 51745
Thread 1 (Thread 16384 (LWP 8428))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-11-08 14:33 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "Gnumeric". Setting to default milestone for this product, '---' Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Appears to be a unique stack trace, according to the simple-dup-finder.
Version is 1.3.93, platform is up-to-date Debian unstable. And, it's not on specific files, just typing "gnumeric" in a terminal is enough. And, it worked just a week ago... /Mikael
Ok, I can see how this could happen if you previously had Gnumeric compiled with gnome support and now have it without.
Will be fixed in cvs shortly. To get things running, use gconf editor to get rid of history items for gnumeric.
Workaround (deleting history from /apps/gnumeric/core/file/history) works, thanks!!
*** Bug 158864 has been marked as a duplicate of this bug. ***