GNOME Bugzilla – Bug 520028
crash in Tasks: send & receive mail
Last modified: 2008-03-03 20:51:15 UTC
Version: 2.10 What were you doing when the application crashed? send & receive mail 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 138932224 vsize: 138932224 resident: 41410560 share: 32870400 rss: 41410560 rss_rlim: 4294967295 CPU usage: start_time: 1204522085 rtime: 158 utime: 139 stime: 19 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209014560 (LWP 3486)] [New Thread -1263936624 (LWP 3542)] [New Thread -1242956912 (LWP 3541)] [New Thread -1253446768 (LWP 3512)] [New Thread -1230677104 (LWP 3510)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 191115
Thread 1 (Thread -1209014560 (LWP 3486))
----------- .xsession-errors (11 sec old) --------------------- localuser:try being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2862 error getting update info: Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again CalDAV Eplugin starting up ... ** (evolution:3486): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3486): 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 ***