GNOME Bugzilla – Bug 494022
crash in Tasks: Starting evolution
Last modified: 2007-11-07 21:49:49 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-07-02 (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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 152858624 vsize: 152858624 resident: 49176576 share: 30134272 rss: 49176576 rss_rlim: 4294967295 CPU usage: start_time: 1194327853 rtime: 134 utime: 118 stime: 16 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 -1208596768 (LWP 3254)] [New Thread -1264989296 (LWP 3303)] [New Thread -1233126512 (LWP 3302)] [New Thread -1254499440 (LWP 3279)] [New Thread -1243616368 (LWP 3278)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 175627
Thread 1 (Thread -1208596768 (LWP 3254))
----------- .xsession-errors (6 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name CalDAV Eplugin starting up ... ** (evolution:3254): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3254): 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 ***