GNOME Bugzilla – Bug 605372
crash in Evolution Mail: Clicked on a spam email
Last modified: 2010-02-20 03:44:59 UTC
What were you doing when the application crashed? Clicked on a spam email 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: 196681728 vsize: 196681728 resident: 37851136 share: 23195648 rss: 37851136 rss_rlim: 18446744073709551615 CPU usage: start_time: 1261667106 rtime: 495 utime: 351 stime: 144 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 0xf0be8b70 (LWP 11926)] [New Thread 0xec4feb70 (LWP 11920)] [New Thread 0xf3e01b70 (LWP 11913)] [New Thread 0xeccffb70 (LWP 11912)] [New Thread 0xef2b3b70 (LWP 11881)] [New Thread 0xefab4b70 (LWP 11880)] [New Thread 0xf03e7b70 (LWP 11879)] [New Thread 0xf13e9b70 (LWP 11874)] [New Thread 0xf2daab70 (LWP 11872)] [New Thread 0xf35abb70 (LWP 11870)] [New Thread 0xf47d1b70 (LWP 11868)] [New Thread 0xf4fd2b70 (LWP 11867)] 0xffffe425 in __kernel_vsyscall ()
+ Trace 219766
Thread 1 (Thread 0xf5991760 (LWP 11861))
Inferior 1 [process 11861] 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 (204790 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... --------------------------------------------------
could be a dupe of bug 601639
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 ***