GNOME Bugzilla – Bug 492886
crash in Tasks: Clicked "Send/Receive"
Last modified: 2007-11-03 16:03:25 UTC
Version: 2.10 What were you doing when the application crashed? Clicked "Send/Receive" 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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Glider Icon Theme: gnome Memory status: size: 124542976 vsize: 124542976 resident: 34402304 share: 27975680 rss: 34402304 rss_rlim: 4294967295 CPU usage: start_time: 1194050833 rtime: 86 utime: 72 stime: 14 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 -1208834336 (LWP 3378)] [New Thread -1251263600 (LWP 3420)] [New Thread -1272243312 (LWP 3419)] [New Thread -1219216496 (LWP 3390)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 174745
Thread 1 (Thread -1208834336 (LWP 3378))
----------- .xsession-errors (7 sec old) --------------------- localuser:nange being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/3122 Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. 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 CalDAV Eplugin starting up ... ** (evolution:3378): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3378): 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 ***