GNOME Bugzilla – Bug 604926
crash in Evolution:
Last modified: 2010-03-24 13:02:42 UTC
What were you doing when the application crashed? 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: 831270912 vsize: 831270912 resident: 42766336 share: 17518592 rss: 42766336 rss_rlim: 18446744073709551615 CPU usage: start_time: 1261126399 rtime: 2785 utime: 2541 stime: 244 cutime:1874 cstime: 86 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x7ff8f0711910 (LWP 8139)] [New Thread 0x7ff8eef0e910 (LWP 8137)] [New Thread 0x7ff8f9014910 (LWP 4123)] [New Thread 0x7ff8ff409910 (LWP 4116)] [New Thread 0x7ff8fa016910 (LWP 4115)] [New Thread 0x7ff8fc403910 (LWP 3711)] [New Thread 0x7ff8fcc04910 (LWP 3710)] [New Thread 0x7ff8fd405910 (LWP 3709)] [New Thread 0x7ff8fdc06910 (LWP 3708)] [New Thread 0x7ff8fe407910 (LWP 3707)] [New Thread 0x7ff8fec08910 (LWP 3706)] [New Thread 0x7ff8ffc0a910 (LWP 3704)] [New Thread 0x7ff90040b910 (LWP 3703)] [New Thread 0x7ff900e35910 (LWP 3702)] [New Thread 0x7ff901636910 (LWP 3701)] 0x00007ff9181eb51d in __libc_waitpid (pid=8145, stat_loc=<value optimized out>, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 in ../sysdeps/unix/sysv/linux/waitpid.c
+ Trace 219668
Thread 2 (Thread 0x7ff8f0711910 (LWP 8139))
Inferior 1 [process 3430] 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:3430): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:3430): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:3430): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:3430): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (devilspie:3271): CRITICAL **: e_sexp_eval: assertion `f->tree != NULL' failed ** (devilspie:3271): CRITICAL **: e_sexp_eval: assertion `f->tree != NULL' failed --------------------------------------------------
looks duplicate of bug 602394 as per second <signal handler> call
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 602394 ***