GNOME Bugzilla – Bug 605482
crash in Evolution: checking mail
Last modified: 2009-12-27 19:15:05 UTC
What were you doing when the application crashed? checking mail Distribution: Debian squeeze/sid Gnome Release: 2.28.0 2009-11-21 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.32-trunk-amd64 #1 SMP Thu Dec 17 06:29:18 UTC 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Mist GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 834011136 vsize: 834011136 resident: 55304192 share: 19283968 rss: 55304192 rss_rlim: 18446744073709551615 CPU usage: start_time: 1261827038 rtime: 3411 utime: 3078 stime: 333 cutime:2440 cstime: 140 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x7f4614f84910 (LWP 11323)] [New Thread 0x7f460de79910 (LWP 11322)] [New Thread 0x7f4613f82910 (LWP 4641)] [New Thread 0x7f4615785910 (LWP 3486)] [New Thread 0x7f4615f86910 (LWP 3485)] [New Thread 0x7f4616787910 (LWP 3483)] [New Thread 0x7f4616f88910 (LWP 3482)] [New Thread 0x7f4617789910 (LWP 3481)] [New Thread 0x7f4617f8a910 (LWP 3480)] [New Thread 0x7f4618f8c910 (LWP 3478)] [New Thread 0x7f461978d910 (LWP 3477)] [New Thread 0x7f461a1b7910 (LWP 3474)] [New Thread 0x7f461abd6910 (LWP 3473)] [New Thread 0x7f462027d910 (LWP 3384)] [New Thread 0x7f4620a7e910 (LWP 3382)] 0x00007f46377c451d in __libc_waitpid (pid=11328, stat_loc=<value optimized out>, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 in ../sysdeps/unix/sysv/linux/waitpid.c
+ Trace 219778
Thread 1 (Thread 0x7f463c96b7f0 (LWP 3189))
Inferior 1 [process 3189] 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 --------------------- ** (evolution:3189): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:3189): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:3189): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:3189): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:3189): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed --------------------------------------------------
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 557613 ***