GNOME Bugzilla – Bug 479449
crash in Tasks: email ophalen
Last modified: 2007-09-24 17:31:39 UTC
Version: 2.10 What were you doing when the application crashed? email ophalen 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 119824384 vsize: 119824384 resident: 37888000 share: 30588928 rss: 37888000 rss_rlim: 4294967295 CPU usage: start_time: 1190528507 rtime: 117 utime: 105 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 -1208895776 (LWP 2953)] [New Thread -1287238768 (LWP 3057)] [New Thread -1221944432 (LWP 2999)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 164789
Thread 1 (Thread -1208895776 (LWP 2953))
----------- .xsession-errors (192 sec old) --------------------- localuser:gebruiker being added to access control list SESSION_MANAGER=local/server1:/tmp/.ICE-unix/2742 Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. CalDAV Eplugin starting up ... ** (evolution:2953): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2953): 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 ***