GNOME Bugzilla – Bug 502173
crash in Tasks: I start EVOLUTION
Last modified: 2007-12-07 11:09:16 UTC
Version: 2.10 What were you doing when the application crashed? I start 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.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: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 201715712 vsize: 201715712 resident: 64815104 share: 57962496 rss: 64815104 rss_rlim: 4294967295 CPU usage: start_time: 1196968167 rtime: 86 utime: 76 stime: 10 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 -1208707360 (LWP 2902)] [New Thread -1337988208 (LWP 2957)] [New Thread -1262961776 (LWP 2935)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 181025
Thread 1 (Thread -1208707360 (LWP 2902))
----------- .xsession-errors --------------------- localuser:olivier being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2703 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:2902): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2902): 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 431459 ***