GNOME Bugzilla – Bug 480249
crash in Tasks: Reading email
Last modified: 2007-10-02 03:17:10 UTC
Version: 2.10 What were you doing when the application crashed? Reading email 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.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 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: 149200896 vsize: 149200896 resident: 48734208 share: 29863936 rss: 48734208 rss_rlim: 4294967295 CPU usage: start_time: 1190732413 rtime: 211 utime: 202 stime: 9 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208699168 (LWP 3250)] [New Thread -1266693232 (LWP 3311)] [New Thread -1322222704 (LWP 3302)] [New Thread -1311085680 (LWP 3301)] [New Thread -1290105968 (LWP 3298)] [New Thread -1235223664 (LWP 3273)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 165385
Thread 1 (Thread -1208699168 (LWP 3250))
----------- .xsession-errors (29 sec old) --------------------- localuser:davidhan being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/3011 CalDAV Eplugin starting up ... ** (evolution:3250): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3250): 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 467763 ***