GNOME Bugzilla – Bug 501209
crash in Tasks:
Last modified: 2007-12-03 15:08:53 UTC
Version: 2.10 What were you doing when the application crashed? 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.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 158142464 vsize: 158142464 resident: 36876288 share: 29446144 rss: 36876288 rss_rlim: 4294967295 CPU usage: start_time: 1196677557 rtime: 133 utime: 116 stime: 17 cutime:0 cstime: 2 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 -1208666400 (LWP 3015)] [New Thread -1284527216 (LWP 3082)] [New Thread -1274037360 (LWP 3081)] [New Thread -1305506928 (LWP 3045)] [New Thread -1253057648 (LWP 3039)] [New Thread -1242567792 (LWP 3038)] [New Thread -1220080752 (LWP 3036)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 180524
Thread 1 (Thread -1208666400 (LWP 3015))
----------- .xsession-errors (130 sec old) --------------------- localuser:lefty being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2811 CalDAV Eplugin starting up ... ** (evolution:3015): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3015): 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 ***