GNOME Bugzilla – Bug 449071
crash in Gnumeric Spreadsheet:
Last modified: 2007-06-19 17:24:28 UTC
Version: 1.7.10 What were you doing when the application crashed? Distribution: Unknown Gnome Release: 2.18.2 2007-06-02 (FreeBSD GNOME Project) BugBuddy Version: 2.18.1 System: FreeBSD 6.2-STABLE FreeBSD 6.2-STABLE #0: Wed Jun 6 16:11:24 JST 2007 root@ryouko:/usr/obj/usr/src/sys/TSURUYA i386 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Enabled GTK+ Theme: Mist Icon Theme: Mist Memory status: size: 116460 vsize: 116460 resident: 57376 share: 95341965 rss: 57376 rss_rlim: 14344 CPU usage: start_time: 0 rtime: 1729 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 133 Backtrace was generated from '/usr/local/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)...(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 LWP 100235] (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)...[Switching to LWP 100235] 0x2937051d in wait4 () from /lib/libc.so.6
+ Trace 142105
Thread 1 (LWP 100235)
----------- .xsession-errors (2449 sec old) --------------------- ** Message: volume = 0 GTK Accessibility Module initialized Bonobo accessibility support initialized Bus error (core dumped) GTK Accessibility Module initialized Hangup GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Usage: -i /file/to/install GTK Accessibility Module initialized GTK Accessibility Module initialized Bonobo accessibility support initialized --------------------------------------------------
Unfortunately those back traces do not tell us much. You might try disabling accessibility, but without information on what you were doing when gnumeric crashed we can not do much.
*** This bug has been marked as a duplicate of 439416 ***