GNOME Bugzilla – Bug 520447
crash in Tasks:
Last modified: 2008-03-05 16:55:16 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.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: Clearlooks Icon Theme: Fedora Memory status: size: 153473024 vsize: 153473024 resident: 42622976 share: 32608256 rss: 42622976 rss_rlim: 4294967295 CPU usage: start_time: 1204690291 rtime: 181 utime: 120 stime: 61 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 -1209010464 (LWP 10009)] [New Thread -1240470640 (LWP 10051)] [New Thread -1292919920 (LWP 10047)] [New Thread -1250960496 (LWP 10046)] [New Thread -1321784432 (LWP 10044)] [New Thread -1271940208 (LWP 10033)] [New Thread -1217827952 (LWP 10027)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 191342
Thread 1 (Thread -1209010464 (LWP 10009))
----------- .xsession-errors (73275 sec old) --------------------- (gnome-panel:2832): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (gnome-panel:2832): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (gnome-panel:2832): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (gnome-panel:2832): 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 ***