GNOME Bugzilla – Bug 505615
crash in Tasks:
Last modified: 2007-12-25 23:56:24 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Fedora Memory status: size: 123850752 vsize: 123850752 resident: 38150144 share: 30466048 rss: 38150144 rss_rlim: 4294967295 CPU usage: start_time: 1198610085 rtime: 142 utime: 125 stime: 17 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 -1208359200 (LWP 4726)] [New Thread -1235223664 (LWP 5070)] [New Thread -1266693232 (LWP 4748)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 183028
Thread 1 (Thread -1208359200 (LWP 4726))
----------- .xsession-errors (3603 sec old) --------------------- Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Max failures exceeded, exiting now report junk?? Didn't get what you wanted this Christmas? CalDAV Eplugin starting up ... ** (evolution:4235): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:4235): DEBUG: mailto URL program: evolution CalDAV Eplugin starting up ... ** (evolution:4726): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:4726): DEBUG: mailto URL program: evolution --------------------------------------------------
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 ***