GNOME Bugzilla – Bug 605521
crash in Evolution: checking mail
Last modified: 2009-12-27 18:51:51 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: 876924928 vsize: 876924928 resident: 71786496 share: 30220288 rss: 71786496 rss_rlim: 18446744073709551615 CPU usage: start_time: 1261884008 rtime: 2503 utime: 2239 stime: 264 cutime:3087 cstime: 154 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x7f3d699d5910 (LWP 13199)] [New Thread 0x7f3d6b7fe910 (LWP 3388)] [New Thread 0x7f3d7c061910 (LWP 3308)] [New Thread 0x7f3d73b0c910 (LWP 3307)] [New Thread 0x7f3d757fa910 (LWP 3255)] [New Thread 0x7f3d75ffb910 (LWP 3254)] [New Thread 0x7f3d767fc910 (LWP 3253)] [New Thread 0x7f3d76ffd910 (LWP 3252)] [New Thread 0x7f3d777fe910 (LWP 3251)] [New Thread 0x7f3d77fff910 (LWP 3250)] [New Thread 0x7f3d7d67e910 (LWP 3248)] [New Thread 0x7f3d7de7f910 (LWP 3247)] [New Thread 0x7f3d7e8a9910 (LWP 3246)] [New Thread 0x7f3d7f0aa910 (LWP 3245)] 0x00007f3d95c9e51d in __libc_waitpid (pid=13213, stat_loc=<value optimized out>, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 in ../sysdeps/unix/sysv/linux/waitpid.c
+ Trace 219787
Thread 1 (Thread 0x7f3d9ae457f0 (LWP 3219))
Inferior 1 [process 3219] 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 --------------------- ** (devilspie:3057): CRITICAL **: e_sexp_eval: assertion `f->tree != NULL' failed ** (evolution:3219): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:3219): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:3219): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:3219): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:3219): 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 ***