GNOME Bugzilla – Bug 520107
crash in Tasks: Checking my e-mail
Last modified: 2008-03-03 20:50:44 UTC
Version: 2.10 What were you doing when the application crashed? Checking my e-mail 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 112529408 vsize: 112529408 resident: 34283520 share: 26378240 rss: 34283520 rss_rlim: 4294967295 CPU usage: start_time: 1204556060 rtime: 171 utime: 118 stime: 53 cutime:1 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 -1208903968 (LWP 23194)] [New Thread -1240470640 (LWP 23218)] [New Thread -1217672304 (LWP 23215)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 191159
Thread 1 (Thread -1208903968 (LWP 23194))
----------- .xsession-errors (1629422 sec old) --------------------- (evolution:4231): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (evolution:4231): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (evolution:4231): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (evolution:4231): 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 ***