GNOME Bugzilla – Bug 601780
crash in Evolution: This is reproducible: Op...
Last modified: 2009-11-13 11:36:16 UTC
What were you doing when the application crashed? This is reproducible: Open evolution. Open a new message (to send). Type in an address or a subject or something else - just that it is not in "unchanged" mode. Now go back to the main window and use File > Quit. Evolution crashes reproducibly. Usually evolution asks what to do with the unsent message. Distribution: Debian squeeze/sid Gnome Release: 2.28.0 2009-10-27 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.31-1-amd64 #1 SMP Sat Oct 24 17:50:31 UTC 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: 674377728 vsize: 674377728 resident: 70131712 share: 26116096 rss: 70131712 rss_rlim: 18446744073709551615 CPU usage: start_time: 1258103370 rtime: 490 utime: 431 stime: 59 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 0x7fb421f99910 (LWP 25775)] [New Thread 0x7fb41eaf6910 (LWP 25760)] [New Thread 0x7fb423fff910 (LWP 25759)] [New Thread 0x7fb422ffd910 (LWP 25737)] [New Thread 0x7fb428ef8910 (LWP 25734)] [New Thread 0x7fb42a575910 (LWP 25733)] [New Thread 0x7fb42ad76910 (LWP 25731)] [New Thread 0x7fb42b783910 (LWP 25730)] [New Thread 0x7fb42c1ad910 (LWP 25729)] [New Thread 0x7fb42c9ae910 (LWP 25728)] 0x00007fb441fba52d in __libc_waitpid (pid=25776, stat_loc=<value optimized out>, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 in ../sysdeps/unix/sysv/linux/waitpid.c
+ Trace 219063
Thread 1 (Thread 0x7fb4470607f0 (LWP 25722))
Inferior 1 [process 25722] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** e-attachment-view.c **: e_attachment_view_get_store: assertion `E_IS_ATTACHMENT_VIEW (view)' failed ** composer **: e_composer_header_table_get_subject: assertion `E_IS_COMPOSER_HEADER_TABLE (table)' failed ** composer **: e_composer_header_table_get_account: assertion `E_IS_COMPOSER_HEADER_TABLE (table)' failed ** composer **: e_composer_header_table_get_reply_to: assertion `E_IS_COMPOSER_HEADER_TABLE (table)' failed ** composer **: e_composer_header_table_get_header: assertion `E_IS_COMPOSER_HEADER_TABLE (table)' failed ** composer **: e_composer_header_get_visible: assertion `E_IS_COMPOSER_HEADER (header)' failed ** composer **: e_composer_header_table_get_header: assertion `E_IS_COMPOSER_HEADER_TABLE (table)' failed ** composer **: e_composer_header_get_visible: assertion `E_IS_COMPOSER_HEADER (header)' failed ** Gtk **: gtk_ui_manager_get_action_groups: assertion `GTK_IS_UI_MANAGER (self)' failed ** gtkhtml-editor **: gtkhtml_editor_get_action: assertion `action != NULL' failed ** Gtk **: gtk_toggle_action_get_active: assertion `GTK_IS_TOGGLE_ACTION (action)' failed ** Gtk **: gtk_ui_manager_get_action_groups: assertion `GTK_IS_UI_MANAGER (self)' failed ** gtkhtml-editor **: gtkhtml_editor_get_action: assertion `action != NULL' failed ** Gtk **: gtk_toggle_action_get_active: assertion `GTK_IS_TOGGLE_ACTION (action)' failed ** gtkhtml **: gtk_html_export: assertion `html != NULL' failed ----------- .xsession-errors (2795 sec old) --------------------- (firefox-bin:4775): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:4775): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:4775): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:4775): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:4775): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:4775): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:4775): Gdk-WARNING **: XID collision, trouble ahead ...Too much output, ignoring rest... --------------------------------------------------
Created attachment 147649 [details] GDB backtrace The backtrace created with gdb.
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 596566 ***