GNOME Bugzilla – Bug 605371
crash in Evolution Mail: It was idle
Last modified: 2009-12-25 03:13:01 UTC
What were you doing when the application crashed? It was idle Distribution: Debian squeeze/sid Gnome Release: 2.28.0 2009-11-21 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.32 #12 SMP Mon Dec 7 13:51:35 EST 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 402669568 vsize: 402669568 resident: 202309632 share: 15167488 rss: 202309632 rss_rlim: 18446744073709551615 CPU usage: start_time: 1261409441 rtime: 115482 utime: 73304 stime: 42178 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 0xe61fcb70 (LWP 11499)] [New Thread 0xe33fdb70 (LWP 11492)] [New Thread 0xf0b47b70 (LWP 27747)] [New Thread 0xf3fbdb70 (LWP 27746)] [New Thread 0xef307b70 (LWP 25220)] [New Thread 0xf043bb70 (LWP 25219)] [New Thread 0xefb08b70 (LWP 25216)] [New Thread 0xf25fdb70 (LWP 25213)] [New Thread 0xf2dfeb70 (LWP 25211)] [New Thread 0xf35ffb70 (LWP 25210)] [New Thread 0xf47e2b70 (LWP 25208)] [New Thread 0xf4fe3b70 (LWP 25207)] 0xffffe425 in __kernel_vsyscall ()
+ Trace 219765
Thread 3 (Thread 0xe33fdb70 (LWP 11492))
Inferior 1 [process 25193] 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 (204069 sec old) --------------------- ** (evolution:25193): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:25193): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:25193): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:25193): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:25193): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:25193): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:25193): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ...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 600322 ***