GNOME Bugzilla – Bug 468928
crash in Tasks:
Last modified: 2007-10-11 17:03:13 UTC
Version: 2.10 What were you doing when the application crashed? 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.22.1-41.fc7 #1 SMP Fri Jul 27 18:21:43 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 547704832 vsize: 547704832 resident: 35491840 share: 26468352 rss: 35491840 rss_rlim: 18446744073709551615 CPU usage: start_time: 1187716258 rtime: 115 utime: 69 stime: 46 cutime:3 cstime: 13 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496402576 (LWP 3174)] [New Thread 1094719824 (LWP 3198)] [New Thread 1084229968 (LWP 3195)] (no debugging symbols found) 0x000000332b20d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 156898
Thread 1 (Thread 46912496402576 (LWP 3174))
----------- .xsession-errors --------------------- (bug-buddy:3224): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (bug-buddy:3224): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (bug-buddy:3224): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (bug-buddy:3224): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (bug-buddy:3224): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid --------------------------------------------------
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 ***