GNOME Bugzilla – Bug 516783
crash in Tasks: closing evolution
Last modified: 2008-02-16 04:41:37 UTC
Version: 2.10 What were you doing when the application crashed? closing evolution 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.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 100945920 vsize: 100945920 resident: 31457280 share: 22966272 rss: 31457280 rss_rlim: 4294967295 CPU usage: start_time: 1203125434 rtime: 888 utime: 843 stime: 45 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 -1209047328 (LWP 2826)] [New Thread -1265349744 (LWP 3001)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 189367
Thread 2 (Thread -1265349744 (LWP 3001))
----------- .xsession-errors (327 sec old) --------------------- CConn: connected to host 24.62.152.214 port 5900 CConnection: Server supports RFB protocol version 3.8 CConnection: Using RFB protocol version 3.8 Fri Feb 15 20:34:57 2008 TXImage: Using default colormap and visual, TrueColor, depth 24. CConn: Using pixel format depth 6 (8bpp) rgb222 CConn: Using ZRLE encoding Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Fri Feb 15 20:39:59 2008 main: End of stream Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. --------------------------------------------------
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 445309 ***