GNOME Bugzilla – Bug 519216
crash in Gnumeric Spreadsheet:
Last modified: 2008-02-28 14:38:05 UTC
Version: 1.8.1 What were you doing when the application crashed? Distribution: Unknown Gnome Release: 2.20.3 2008-01-14 (FreeBSD GNOME Project) BugBuddy Version: 2.20.1 System: FreeBSD 6.3-STABLE FreeBSD 6.3-STABLE #0: Mon Feb 18 23:10:11 JST 2008 root@ryouko:/usr/obj/usr/src/sys/TSURUYA i386 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Enabled GTK+ Theme: Mist Icon Theme: Mist Memory status: size: 93179904 vsize: 93179904 resident: 35672064 share: 82651173 rss: 35672064 rss_rlim: 8709 CPU usage: start_time: 0 rtime: 133 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)...(no debugging symbols found)...(no debugging symbols found)...[New LWP 100130] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(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 100130] 0x2938a639 in wait4 () from /lib/libc.so.6
+ Trace 190705
Thread 1 (LWP 100130)
----------- .xsession-errors --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 warning: Unable to get location for thread creation breakpoint: generic error --------------------------------------------------
There is no point in keeping reporting this bug until and unless you can provide the very simple feedback we are asking for. Does this problem happen if you use the default theme? *** This bug has been marked as a duplicate of 450348 ***