GNOME Bugzilla – Bug 498949
crash in Tasks: booting up and then logg...
Last modified: 2007-11-22 14:23:23 UTC
Version: 2.10 What were you doing when the application crashed? booting up and then logging in for first time 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.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 111984640 vsize: 111984640 resident: 32653312 share: 25714688 rss: 32653312 rss_rlim: 4294967295 CPU usage: start_time: 1195733471 rtime: 120 utime: 85 stime: 35 cutime:3 cstime: 4 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 -1208191264 (LWP 3157)] [New Thread -1238332528 (LWP 3323)] [New Thread -1216959600 (LWP 3320)] (no debugging symbols found) 0x00e9b402 in __kernel_vsyscall ()
+ Trace 179235
Thread 1 (Thread -1208191264 (LWP 3157))
----------- .xsession-errors --------------------- (evolution:3157): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (evolution:3157): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (evolution:3157): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (evolution:3157): 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 ***