GNOME Bugzilla – Bug 503199
crash in Tasks: nothing
Last modified: 2007-12-12 20:55:33 UTC
Version: 2.10 What were you doing when the application crashed? nothing Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 132218880 vsize: 132218880 resident: 51499008 share: 28364800 rss: 51499008 rss_rlim: 4294967295 CPU usage: start_time: 1197439719 rtime: 74 utime: 63 stime: 11 cutime:0 cstime: 1 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 -1208301856 (LWP 3599)] [New Thread -1272976496 (LWP 3623)] [New Thread -1218966640 (LWP 3617)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 181628
Thread 1 (Thread -1208301856 (LWP 3599))
----------- .xsession-errors --------------------- No package matched to remove No package matched to remove No package matched to remove No package matched to remove CalDAV Eplugin starting up ... ** (evolution:3517): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3517): 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 in emp_apps_open_in CalDAV Eplugin starting up ... ** (evolution:3599): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3599): 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 431459 ***