GNOME Bugzilla – Bug 472037
crash in Tasks: just opened Evolution
Last modified: 2007-09-24 18:27:10 UTC
Version: 2.10 What were you doing when the application crashed? just opened 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.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 130486272 vsize: 130486272 resident: 37646336 share: 31039488 rss: 37646336 rss_rlim: 4294967295 CPU usage: start_time: 1188511904 rtime: 110 utime: 90 stime: 20 cutime:2 cstime: 9 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 2979)] [New Thread -1238619248 (LWP 3054)] [New Thread -1267881072 (LWP 3053)] [New Thread -1227719792 (LWP 3020)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 159226
Thread 1 (Thread -1209108768 (LWP 2979))
----------- .xsession-errors (138 sec old) --------------------- localuser:Steve being added to access control list SESSION_MANAGER=local/localHost:/tmp/.ICE-unix/2740 CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:2979): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2979): 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 ***