GNOME Bugzilla – Bug 466414
crash in Tasks: Rweciving mail.
Last modified: 2007-09-24 19:04:08 UTC
Version: 2.10 What were you doing when the application crashed? Rweciving 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.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 114622464 vsize: 114622464 resident: 35360768 share: 28704768 rss: 35360768 rss_rlim: 4294967295 CPU usage: start_time: 1187045969 rtime: 64 utime: 56 stime: 8 cutime:5 cstime: 14 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208150304 (LWP 12066)] [New Thread -1250960496 (LWP 12124)] [New Thread -1261450352 (LWP 12122)] [New Thread -1218839664 (LWP 12100)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 154999
Thread 1 (Thread -1208150304 (LWP 12066))
----------- .xsession-errors (7 sec old) --------------------- localuser:Steve being added to access control list SESSION_MANAGER=local/localhostlocaldomain:/tmp/.ICE-unix/11613 ** (gnome-session:11613): WARNING **: Esound failed to start. ** (gnome-session:11613): WARNING **: Host name lookup failure on localhost. CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:12066): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:12066): 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 ***