GNOME Bugzilla – Bug 510735
crash in Tasks: recieving email
Last modified: 2008-01-20 19:53:40 UTC
Version: 2.10 What were you doing when the application crashed? recieving email 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.21-6.fc7xen #1 SMP Mon Nov 19 07:14:27 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 233578496 vsize: 233578496 resident: 68378624 share: 61485056 rss: 68378624 rss_rlim: 4294967295 CPU usage: start_time: 1200804758 rtime: 68 utime: 61 stime: 7 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208453408 (LWP 3278)] [New Thread -1330881648 (LWP 3310)] [New Thread -1309901936 (LWP 3303)] [New Thread -1278432368 (LWP 3300)] [New Thread -1267942512 (LWP 3299)] (no debugging symbols found) 0x00136402 in __kernel_vsyscall ()
+ Trace 186036
Thread 1 (Thread -1208453408 (LWP 3278))
----------- .xsession-errors (30 sec old) --------------------- localuser:lawrie being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/3043 Error: permissions error in pam_timestamp_check CalDAV Eplugin starting up ... ** (evolution:3278): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3278): 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 ***