GNOME Bugzilla – Bug 516362
crash in Tasks: starting evolution
Last modified: 2008-02-14 07:34:36 UTC
Version: 2.10 What were you doing when the application crashed? starting evolution 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.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 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: 149200896 vsize: 149200896 resident: 50622464 share: 41664512 rss: 50622464 rss_rlim: 4294967295 CPU usage: start_time: 1202968760 rtime: 153 utime: 134 stime: 19 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 -1208985888 (LWP 3491)] [New Thread -1241551984 (LWP 3546)] [New Thread -1230648432 (LWP 3515)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 189144
Thread 1 (Thread -1208985888 (LWP 3491))
----------- .xsession-errors (10 sec old) --------------------- localuser:try being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2866 ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name error getting update info: Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again CalDAV Eplugin starting up ... ** (evolution:3491): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3491): 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 ***