GNOME Bugzilla – Bug 507688
crash in Tasks: booted, and started Evol...
Last modified: 2008-02-07 06:06:38 UTC
Version: 2.10 What were you doing when the application crashed? booted, and started 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 20:27:10 EST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 557965312 vsize: 557965312 resident: 41140224 share: 30310400 rss: 41140224 rss_rlim: 18446744073709551615 CPU usage: start_time: 1199638028 rtime: 129 utime: 103 stime: 26 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496428400 (LWP 3184)] [New Thread 1105209680 (LWP 3208)] [New Thread 1084229968 (LWP 3205)] (no debugging symbols found) 0x0000003abec0d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 184290
Thread 1 (Thread 46912496428400 (LWP 3184))
----------- .xsession-errors --------------------- localuser:mike being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2975 CalDAV Eplugin starting up ... ** (evolution:3184): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3184): 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 warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff8fbfd000 --------------------------------------------------
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 431459 ***