GNOME Bugzilla – Bug 629109
crash in Evolution Mail: Opening an email with an...
Last modified: 2010-09-08 22:10:56 UTC
What were you doing when the application crashed? Opening an email with an attachement Distribution: Debian squeeze/sid Gnome Release: 2.30.2 2010-07-17 (Debian) BugBuddy Version: 2.30.0 System: Linux 2.6.35-trunk-amd64 #1 SMP Tue Aug 17 08:22:25 UTC 2010 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10707000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 834367488 vsize: 834367488 resident: 127754240 share: 17965056 rss: 127754240 rss_rlim: 18446744073709551615 CPU usage: start_time: 1283952818 rtime: 25281 utime: 19554 stime: 5727 cutime:3913 cstime: 3892 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x7fd78d7f4710 (LWP 15753)] [New Thread 0x7fd775112710 (LWP 15747)] [New Thread 0x7fd777bf4710 (LWP 4719)] [New Thread 0x7fd78dff5710 (LWP 4718)] [New Thread 0x7fd77da85710 (LWP 3635)] [New Thread 0x7fd77e286710 (LWP 3634)] [New Thread 0x7fd787fff710 (LWP 3629)] [New Thread 0x7fd78cff3710 (LWP 3628)] [New Thread 0x7fd78eff7710 (LWP 3624)] [New Thread 0x7fd78f7f8710 (LWP 3623)] [New Thread 0x7fd790222710 (LWP 3622)] [New Thread 0x7fd790a23710 (LWP 3621)] 0x00007fd79e6ddb4d in waitpid () from /lib/libpthread.so.0
+ Trace 223601
Thread 2 (Thread 0x7fd78d7f4710 (LWP 15753))
Inferior 1 [process 3620] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** camel **: camel_session_lookup_addressbook: assertion `name != NULL' failed ** camel **: camel_session_lookup_addressbook: assertion `name != NULL' failed ** camel **: camel_session_lookup_addressbook: assertion `name != NULL' failed ** camel **: camel_session_lookup_addressbook: assertion `name != NULL' failed ** camel **: camel_session_lookup_addressbook: assertion `name != NULL' failed ** camel **: camel_session_lookup_addressbook: assertion `name != NULL' failed ** camel **: camel_session_lookup_addressbook: assertion `name != NULL' failed ** camel **: camel_session_lookup_addressbook: assertion `name != NULL' failed ** camel **: camel_session_lookup_addressbook: assertion `name != NULL' failed ** camel **: camel_session_lookup_addressbook: assertion `name != NULL' failed ** camel **: camel_session_lookup_addressbook: assertion `name != NULL' failed ** Gtk **: _gtk_file_system_model_remove_editable: assertion `get_node (model, 0)->visible' failed ** camel **: camel_data_wrapper_set_mime_type_field: assertion `mime_type != NULL' failed ** camel **: camel_data_wrapper_set_mime_type_field: assertion `mime_type != NULL' failed ** evolution **: em_format_add_puri: assertion `emf->pending_uri_level != NULL' failed ----------- .xsession-errors (7 sec old) --------------------- (evolution:3620): camel-CRITICAL **: camel_data_wrapper_set_mime_type_field: assertion `mime_type != NULL' failed *** NSPlugin Viewer *** WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue() *** NSPlugin Viewer *** WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue() *** NSPlugin Viewer *** WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue() *** NSPlugin Viewer *** WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue() *** NSPlugin Viewer *** WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue() *** NSPlugin Viewer *** WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue() (nautilus:2440): Nautilus-GDU-WARNING **: unable to query info: The specified location is not supported (nautilus:2440): Nautilus-GDU-WARNING **: unable to query info: The specified location is not supported ** (evolution:3620): CRITICAL **: em_format_add_puri: assertion `emf->pending_uri_level != NULL' failed --------------------------------------------------
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 628723 ***