GNOME Bugzilla – Bug 512541
crash in Tasks: i was opening the letter
Last modified: 2008-01-29 18:21:13 UTC
Version: 2.10 What were you doing when the application crashed? i was opening the letter 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 115380224 vsize: 115380224 resident: 38666240 share: 31801344 rss: 38666240 rss_rlim: 4294967295 CPU usage: start_time: 1201518974 rtime: 115 utime: 103 stime: 12 cutime:0 cstime: 1 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 -1208432928 (LWP 3275)] [New Thread -1282851952 (LWP 3303)] [New Thread -1236272240 (LWP 3294)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 187044
Thread 1 (Thread -1208432928 (LWP 3275))
----------- .xsession-errors (7 sec old) --------------------- localuser:m being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2904 CalDAV Eplugin starting up ... ** (evolution:3090): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3090): 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 CalDAV Eplugin starting up ... ** (evolution:3275): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3275): 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 431459 ***