GNOME Bugzilla – Bug 516363
crash in Tasks:
Last modified: 2008-02-14 07:34:23 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.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: 126885888 vsize: 126885888 resident: 38723584 share: 31907840 rss: 38723584 rss_rlim: 4294967295 CPU usage: start_time: 1202968468 rtime: 41 utime: 37 stime: 4 cutime:0 cstime: 0 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 -1209108768 (LWP 3133)] [New Thread -1259349104 (LWP 3159)] [New Thread -1226191984 (LWP 3154)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 189145
Thread 1 (Thread -1209108768 (LWP 3133))
----------- .xsession-errors --------------------- localuser:admin being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2955 ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name CalDAV Eplugin starting up ... ** (evolution:3133): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3133): 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 ***