GNOME Bugzilla – Bug 606936
crash in Evolution Mail: Was writing a long («mul...
Last modified: 2010-01-14 11:33:08 UTC
What were you doing when the application crashed? Was writing a long («multi-page») e-mail (saved regularly, as luck has it), marked the text PostgreSQL and klicked the «add link» button to add a link to http://www.postgresql.org/. Never came that far, though, as the window for entering the link data never showed any content (just gnome/metacity window decorations on top) and the application crashed from there. I have a big old setup of Evolution that has survived several upgrades, running with ~650 emails in an IMAP-connected account (harald@thingelstad.org) and several times more in ~30 local folders (but none of them as full I believe). Wish you luck with the debugging, I *do* get crashes from time to time. Bit of a slow machine now (Intel 1.2Ghz with only 512 Mbytes of ram) but I hope that still works! :) Distribution: Debian squeeze/sid Gnome Release: 2.28.2 2009-12-18 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.30-1-686 #1 SMP Sat Aug 15 19:11:58 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: Shiki-Dust Icon Theme: gnome-dust GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 244084736 vsize: 244084736 resident: 24444928 share: 11304960 rss: 24444928 rss_rlim: 18446744073709551615 CPU usage: start_time: 1263453888 rtime: 12434 utime: 11255 stime: 1179 cutime:3 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xaedccb70 (LWP 13224)] [New Thread 0xaaa0db70 (LWP 13223)] [New Thread 0xadcffb70 (LWP 13152)] [New Thread 0xae759b70 (LWP 13151)] [New Thread 0xb16ebb70 (LWP 13145)] [New Thread 0xb1eecb70 (LWP 13143)] [New Thread 0xb2f26b70 (LWP 13141)] [New Thread 0xb37aab70 (LWP 13140)] 0xb8009424 in __kernel_vsyscall ()
+ Trace 220076
Thread 1 (Thread 0xb6272760 (LWP 13117))
Inferior 1 [process 13117] 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 (16421 sec old) --------------------- (firefox-bin:3235): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:3235): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:3235): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:3235): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:3235): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:3235): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:3235): Gdk-WARNING **: XID collision, trouble ahead ...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 606639 ***