GNOME Bugzilla – Bug 602848
crash in Evolution: adding new memos
Last modified: 2009-11-24 22:34:16 UTC
What were you doing when the application crashed? adding new memos Distribution: Gentoo Base System release 2.0.1 Gnome Release: 2.28.0 2009-11-04 (Gentoo) BugBuddy Version: 2.28.0 System: Linux 2.6.31-gentoo-r6 #1 SMP Sun Nov 22 15:21:35 EST 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10701000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 619618304 vsize: 619618304 resident: 38731776 share: 24895488 rss: 38731776 rss_rlim: 18446744073709551615 CPU usage: start_time: 1259080440 rtime: 139 utime: 128 stime: 11 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x7f99f146e710 (LWP 18110)] [New Thread 0x7f99f1e75710 (LWP 18099)] [New Thread 0x7f99eb7fe710 (LWP 18098)] [New Thread 0x7f99f4084710 (LWP 18088)] [New Thread 0x7f99f4885710 (LWP 18087)] Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.2200.2-gdb.py", line 9, in <module> from gobject import register File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module> import gdb.backtrace ImportError: No module named backtrace 0x00007f9a00437bbd in waitpid () from /lib/libpthread.so.0
+ Trace 219267
Thread 1 (Thread 0x7f9a0bb61740 (LWP 18083))
Inferior 1 [process 18083] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ----------- .xsession-errors (2058 sec old) --------------------- ** (evolution:3558): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:3558): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:3558): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:3558): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:3558): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:3558): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (rhythmbox:3635): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (rhythmbox:3635): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed bt_audio_service_open: connect() failed: Connection refused (111) using "org.freedesktop.Notifications" for popups load script file: "utils.js" Script file "/share/qterm/scripts/utils.js" is already loaded load script file: "highlight.js" load script file: "smth.js" bt_audio_service_open: connect() failed: Connection refused (111) --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of bug 599627 ***