GNOME Bugzilla – Bug 477156
crash in Tasks: getting mail using evolu...
Last modified: 2007-09-24 17:43:48 UTC
Version: 2.10 What were you doing when the application crashed? getting mail using evolution 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: 116883456 vsize: 116883456 resident: 36896768 share: 29016064 rss: 36896768 rss_rlim: 4294967295 CPU usage: start_time: 1189846894 rtime: 138 utime: 122 stime: 16 cutime:1 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 -1208400160 (LWP 3179)] [New Thread -1262371952 (LWP 3230)] [New Thread -1251484784 (LWP 3229)] [New Thread -1219208304 (LWP 3201)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 163066
Thread 1 (Thread -1208400160 (LWP 3179))
----------- .xsession-errors (11 sec old) --------------------- localuser:pango being added to access control list SESSION_MANAGER=local/zabox:/tmp/.ICE-unix/2697 error getting update info: Cannot retrieve repository metadata (repomd.xml) for repository: %s. Please verify its path and try again CalDAV Eplugin starting up ... ** (evolution:3179): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3179): 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 ***