GNOME Bugzilla – Bug 605470
crash in Evolution: Closing Evolution
Last modified: 2009-12-27 19:13:34 UTC
What were you doing when the application crashed? Closing Evolution Distribution: Gentoo Base System release 2.0.1 Gnome Release: 2.28.0 2009-11-07 (Gentoo) BugBuddy Version: 2.28.0 System: Linux 2.6.30-gentoo-r5 #2 SMP Wed Aug 19 20:55:57 EDT 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10703000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Gentoo Icon Theme: gnome-noble GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 720334848 vsize: 720334848 resident: 65875968 share: 33370112 rss: 65875968 rss_rlim: 18446744073709551615 CPU usage: start_time: 1261821004 rtime: 1073 utime: 948 stime: 125 cutime:109 cstime: 16 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x7f7e7dffb710 (LWP 12955)] [New Thread 0x7f7e85ffb710 (LWP 12599)] [New Thread 0x7f7e8df38710 (LWP 12598)] [New Thread 0x7f7e90147710 (LWP 12576)] [New Thread 0x7f7e90948710 (LWP 12575)] Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.2200.2-gdb.py", line 9, in <module> from gobject import register File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module> import gdb.backtrace ImportError: No module named backtrace 0x00007f7ea6bc2bcd in waitpid () from /lib/libpthread.so.0
+ Trace 219776
Thread 1 (Thread 0x7f7ea9cff780 (LWP 12571))
A debugging session is active. Inferior 1 [process 12571] 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 (13087685 sec old) --------------------- Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen! --- Hash table keys for warning below: --> file:///home/david/Desktop/2009-Screenshot-Contest --> file:///home/david --> x-nautilus-desktop:/// --> file:///home/david/Desktop/2009-Screenshot-Contest/gallery --> file:///home/david/.thunderbird --> file:///home/david/Desktop --> file:///home --> file:///home/david/.thunderbird/d6sqcw4l.default (nautilus:3075): Eel-WARNING **: "nautilus-metafile.c: metafiles" hash table still has 8 elements at quit time (keys above) (nautilus:3075): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 8 elements at quit time --------------------------------------------------
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 596566 ***