GNOME Bugzilla – Bug 493615
crash in Tasks: Just updated packages an...
Last modified: 2007-11-05 23:28:15 UTC
Version: 2.10 What were you doing when the application crashed? Just updated packages and clicked send/receive on 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.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 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: 160329728 vsize: 160329728 resident: 58269696 share: 37957632 rss: 58269696 rss_rlim: 4294967295 CPU usage: start_time: 1194236871 rtime: 507 utime: 372 stime: 135 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 -1208662304 (LWP 2978)] [New Thread -1299969136 (LWP 3352)] [New Thread -1270281328 (LWP 3349)] [New Thread -1217430640 (LWP 3348)] [New Thread -1248904304 (LWP 3002)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 175308
Thread 1 (Thread -1208662304 (LWP 2978))
----------- .xsession-errors (3616 sec old) --------------------- (gnome-panel:2880): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (gnome-panel:2880): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (gnome-panel:2880): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (gnome-panel:2880): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid ...Too much output, ignoring rest... --------------------------------------------------
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 ***