GNOME Bugzilla – Bug 128642
Gnumeric - crash
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 1 (Yarrow) Package: Gnumeric Severity: normal Version: GNOME2.4.0 unspecified Gnome-Distributor: GNOME.Org Synopsis: Gnumeric - crash Bugzilla-Product: Gnumeric Bugzilla-Component: General Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: Backtrace was generated from '/usr/bin/gnumeric' (no debugging symbols found)...Using host libthread_db library "/lib/tls/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)... (no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -1085097792 (LWP 29279)] (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)... 0x009f3c42 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 42367
Thread 1 (Thread -1085097792 (LWP 29279))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-12-05 21:42 ------- The original reporter (cog@olympos.org) 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.
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Could you try to get another stack trace and/or provide a description of how to get the crash? Thanks. (You can see http://bugzilla.gnome.org/getting-traces.cgi for more information about useful stack traces).
The crash has occured whwn I started the application. I have gotton the same stack trace each time.
Okay, I'll reopen. How often does this crash occur? (e.g. does it occur everytime, infrequently, 20% of the time, etc.)
Do you have accessabilty turned on? (There used to be a glib bug that caused gnumeric to crash.) Upgrading to Gnumeric 1.2.2 may work around that issue.
The crash occurs everytime.
Do you have accessabilty turned on?
Without more information I'm betting that this is just another report of the problem with 'linc'. Disable accessibility (which you don't want on anyway) or update your version of linc. *** This bug has been marked as a duplicate of 121675 ***