GNOME Bugzilla – Bug 433568
crash in libetable
Last modified: 2007-09-20 17:34:16 UTC
What were you doing when the application crashed? Distribution: Fedora release 6.93 (Rawhide) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-1.3104.fc7 #1 SMP Sat Apr 21 22:20:43 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10299905 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 125911040 vsize: 125911040 resident: 36016128 share: 21094400 rss: 36016128 rss_rlim: 4294967295 CPU usage: start_time: 1177578629 rtime: 2926 utime: 2610 stime: 316 cutime:202 cstime: 26 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208801568 (LWP 10891)] [New Thread -1261057136 (LWP 11277)] [New Thread -1230247024 (LWP 10981)] [New Thread -1239680112 (LWP 10898)] (no debugging symbols found) 0x005b2402 in __kernel_vsyscall ()
+ Trace 130677
Thread 1 (Thread -1208801568 (LWP 10891))
----------- .xsession-errors (21 sec old) --------------------- (evolution:10891): Bonobo-CRITICAL **: impl_set_prop: assertion `container != CORBA_OBJECT_NIL' failed (evolution:10891): Bonobo-CRITICAL **: impl_set_prop: assertion `container != CORBA_OBJECT_NIL' failed (evolution:10891): Bonobo-CRITICAL **: impl_set_prop: assertion `container != CORBA_OBJECT_NIL' failed (evolution:10891): Bonobo-CRITICAL **: impl_set_prop: assertion `container != CORBA_OBJECT_NIL' failed (evolution:10891): Bonobo-CRITICAL **: impl_set_prop: assertion `container != CORBA_OBJECT_NIL' failed (evolution:10891): Bonobo-CRITICAL **: impl_set_prop: assertion `container != CORBA_OBJECT_NIL' failed (evolution:10891): Bonobo-CRITICAL **: impl_set_prop: assertion `container != CORBA_OBJECT_NIL' failed (evolution:10891): Bonobo-CRITICAL **: impl_set_prop: assertion `container != CORBA_OBJECT_NIL' failed --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please install some debugging packages [1], start the application as normal, and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the Details, now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] debugging packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, pango, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
*** Bug 449372 has been marked as a duplicate of this bug. ***
*** Bug 452442 has been marked as a duplicate of this bug. ***
*** Bug 443415 has been marked as a duplicate of this bug. ***
*** Bug 456073 has been marked as a duplicate of this bug. ***
*** Bug 458179 has been marked as a duplicate of this bug. ***
*** Bug 457158 has been marked as a duplicate of this bug. ***
*** Bug 455167 has been marked as a duplicate of this bug. ***
*** Bug 457282 has been marked as a duplicate of this bug. ***
*** Bug 460588 has been marked as a duplicate of this bug. ***
*** Bug 461629 has been marked as a duplicate of this bug. ***
*** Bug 463164 has been marked as a duplicate of this bug. ***
*** Bug 464294 has been marked as a duplicate of this bug. ***
*** Bug 467257 has been marked as a duplicate of this bug. ***
*** Bug 465735 has been marked as a duplicate of this bug. ***
*** Bug 469590 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please install some debugging packages [1], start the application as normal, and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the Details, now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] debugging packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, pango, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces note: No neat stacktrace in the dups so far.
*** Bug 471680 has been marked as a duplicate of this bug. ***
*** Bug 471982 has been marked as a duplicate of this bug. ***
*** Bug 476779 has been marked as a duplicate of this bug. ***
*** Bug 478466 has been marked as a duplicate of this bug. ***
Since bug 477793 has a better stacktrace, I'm marking this as a dup. *** This bug has been marked as a duplicate of 477793 ***