GNOME Bugzilla – Bug 465759
crash in Tasks: Opening evolution on boo...
Last modified: 2007-09-24 19:05:22 UTC
Version: 2.10 What were you doing when the application crashed? Opening evolution on boot up 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.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 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: 159670272 vsize: 159670272 resident: 37732352 share: 31088640 rss: 37732352 rss_rlim: 4294967295 CPU usage: start_time: 1186860042 rtime: 63 utime: 53 stime: 10 cutime:2 cstime: 6 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 -1208420640 (LWP 2984)] [New Thread -1322288240 (LWP 3054)] [New Thread -1301308528 (LWP 3053)] [New Thread -1311798384 (LWP 3030)] [New Thread -1248859248 (LWP 3023)] [New Thread -1225880688 (LWP 3021)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 154484
Thread 1 (Thread -1208420640 (LWP 2984))
----------- .xsession-errors --------------------- localuser:root being added to access control list SESSION_MANAGER=local/chiefgeek.icms.com:/tmp/.ICE-unix/2776 CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:2984): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2984): 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 ***