GNOME Bugzilla – Bug 494033
crash in Tasks: Just started Evolution
Last modified: 2007-11-07 21:48:44 UTC
Version: 2.10 What were you doing when the application crashed? Just started 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: 132931584 vsize: 132931584 resident: 34263040 share: 26558464 rss: 34263040 rss_rlim: 4294967295 CPU usage: start_time: 1194332191 rtime: 118 utime: 84 stime: 34 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 -1208559904 (LWP 14659)] [New Thread -1289340016 (LWP 14693)] [New Thread -1228932208 (LWP 14690)] [New Thread -1249911920 (LWP 14681)] [New Thread -1239422064 (LWP 14680)] [New Thread -1217328240 (LWP 14676)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 175635
Thread 1 (Thread -1208559904 (LWP 14659))
----------- .xsession-errors (12111 sec old) --------------------- (pup:2975): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (pup:2975): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (pup:2975): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (pup:2975): 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 431459 ***