GNOME Bugzilla – Bug 476872
crash in Tasks: open mail
Last modified: 2007-10-11 17:07:00 UTC
Version: 2.10 What were you doing when the application crashed? open mail Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.5-76.fc7 #1 SMP Thu Aug 30 13:08:59 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 554680320 vsize: 554680320 resident: 41537536 share: 31346688 rss: 41537536 rss_rlim: 18446744073709551615 CPU usage: start_time: 1189793269 rtime: 118 utime: 99 stime: 19 cutime:1 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912514704144 (LWP 6420)] [New Thread 1115699536 (LWP 6469)] [New Thread 1084229968 (LWP 6442)] (no debugging symbols found) 0x000000302f60d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 162860
Thread 1 (Thread 46912514704144 (LWP 6420))
----------- .xsession-errors (38 sec old) --------------------- --- Hash table keys for warning below: --> file:///root (nautilus:6399): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) ** (nautilus:2737): WARNING **: Hit unhandled case 38 (Service not available) in fm_report_error_loading_directory ** (nautilus:2737): WARNING **: Hit unhandled case 38 (Service not available) in fm_report_error_loading_directory CalDAV Eplugin starting up ... ** (evolution:6420): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:6420): DEBUG: mailto URL program: evolution libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files --------------------------------------------------
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 364700 ***