GNOME Bugzilla – Bug 606530
crash in Evolution: after a long inactive ti...
Last modified: 2010-01-10 18:03:29 UTC
What were you doing when the application crashed? after a long inactive time (night to morning) i delete an e mail and i get the crash. it dose it very often. thanks Distribution: Debian squeeze/sid Gnome Release: 2.28.0 2009-11-21 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.30-2-686 #1 SMP Fri Dec 4 00:53:20 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10605000 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: Neu GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 132759552 vsize: 132759552 resident: 26636288 share: 17063936 rss: 26636288 rss_rlim: 18446744073709551615 CPU usage: start_time: 1263050769 rtime: 5419 utime: 3715 stime: 1704 cutime:1 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 0xb3841b70 (LWP 27891)] [New Thread 0xb2834b70 (LWP 15429)] [New Thread 0xb3040b70 (LWP 15428)] [New Thread 0xb5044b70 (LWP 15420)] [New Thread 0xb5845b70 (LWP 15419)] 0xb7fcb424 in __kernel_vsyscall ()
+ Trace 219986
Thread 1 (Thread 0xb623d760 (LWP 15413))
Inferior 1 [process 15413] 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 (144507 sec old) --------------------- (firefox-bin:6304): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:6304): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:6304): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:6304): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:6304): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:6304): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:6304): Gdk-WARNING **: XID collision, trouble ahead ...Too much output, ignoring rest... --------------------------------------------------
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 599345 ***