GNOME Bugzilla – Bug 477359
crash in Tasks:
Last modified: 2007-09-26 18:03:23 UTC
Version: 2.10 What were you doing when the application crashed? 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:47:21 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: 125513728 vsize: 125513728 resident: 41123840 share: 33619968 rss: 41123840 rss_rlim: 4294967295 CPU usage: start_time: 1189904392 rtime: 135 utime: 119 stime: 16 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208273184 (LWP 6260)] [New Thread -1292305520 (LWP 6308)] [New Thread -1229050992 (LWP 6282)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 163223
Thread 1 (Thread -1208273184 (LWP 6260))
----------- .xsession-errors (14 sec old) --------------------- localuser:steve being added to access control list SESSION_MANAGER=local/circle.msktchung.com:/tmp/.ICE-unix/6060 ** (gnome-session:6060): WARNING **: Esound failed to start. CalDAV Eplugin starting up ... ** (evolution:6260): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:6260): 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 ***