GNOME Bugzilla – Bug 606958
crash in Gnumeric: opening a file from term...
Last modified: 2010-01-19 15:57:40 UTC
Version: 1.9.17 What were you doing when the application crashed? opening a file from terminal Distribution: openSUSE 11.2 (x86_64) Gnome Release: 2.28.0 (null) (SUSE) BugBuddy Version: 2.28.0 System: Linux 2.6.31.8-0.1-desktop #1 SMP PREEMPT 2009-12-15 23:55:40 +0100 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: (null) Icon Theme: (null) Memory status: size: 277594112 vsize: 277594112 resident: 21540864 share: 15175680 rss: 21540864 rss_rlim: 18446744073709551615 CPU usage: start_time: 1263479417 rtime: 20 utime: 17 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnumeric-1.9.17' [Thread debugging using libthread_db enabled] 0x00007f387e55570e in waitpid () from /lib64/libpthread.so.0
+ Trace 220081
Thread 1 (Thread 0x7f38802e0790 (LWP 14858))
A debugging session is active. Inferior 1 [process 14858] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** GLib-GObject **: g_object_new_valist: assertion `G_TYPE_IS_OBJECT (object_type)' failed ** gnumeric **: goc_item_new: assertion `(item != NULL)' failed ** GLib-GObject **: g_object_new_valist: assertion `G_TYPE_IS_OBJECT (object_type)' failed ** gnumeric **: goc_item_new: assertion `(item != NULL)' failed ** GLib-GObject **: g_object_new_valist: assertion `G_TYPE_IS_OBJECT (object_type)' failed ** gnumeric **: goc_item_new: assertion `(item != NULL)' failed ** GLib-GObject **: g_object_new_valist: assertion `G_TYPE_IS_OBJECT (object_type)' failed ** gnumeric **: goc_item_new: assertion `(item != NULL)' failed ----------- .xsession-errors (209 sec old) --------------------- Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2400003 (Authentica) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2400003 (Authentica) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x5a0039f (PeaZip) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Window 0x5a0046c (PeaZip) sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 32767 x 32767; this doesn't make much sense. Window manager warning: Window 0x5a0046c (PeaZip) sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 32767 x 32767; this doesn't make much sense. Window manager warning: Window 0x5a0046c (PeaZip) sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 32767 x 32767; this doesn't make much sense. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x5a0046c (PeaZip) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Window 0x5a00801 (PeaZip) sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 32767 x 32767; this doesn't make much sense. Window manager warning: Window 0x5a00801 (PeaZip) sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 32767 x 32767; this doesn't make much sense. Window manager warning: Window 0x5a00801 (PeaZip) sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 32767 x 32767; this doesn't make much sense. --------------------------------------------------
On upgrade of gnumeric OpenSUSE fails to require an appropriate upgrade of goffice. You can fix this problem in your installation by also upgrading goffice. Note that this is an OpenSUSE packaging bug. Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 604894 ***
mat.icardi@gmail.com: to help fix the issue in openSUSE, can you tell me where you got the gnumeric from, and how did you install it? Thanks!