GNOME Bugzilla – Bug 477665
crash in Tasks:
Last modified: 2007-09-24 17:39:01 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: 115974144 vsize: 115974144 resident: 36257792 share: 28901376 rss: 36257792 rss_rlim: 4294967295 CPU usage: start_time: 1190008759 rtime: 107 utime: 98 stime: 9 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 -1208981792 (LWP 3670)] [New Thread -1273111664 (LWP 3697)] [New Thread -1262621808 (LWP 3695)] [New Thread -1219794032 (LWP 3688)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 163463
Thread 1 (Thread -1208981792 (LWP 3670))
----------- .xsession-errors (6 sec old) --------------------- localuser:pango being added to access control list SESSION_MANAGER=local/zabox:/tmp/.ICE-unix/2712 CalDAV Eplugin starting up ... ** (evolution:2987): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2987): 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 CalDAV Eplugin starting up ... ** (evolution:3670): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3670): 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 ***