GNOME Bugzilla – Bug 508843
crash in Email: crash when opeing progra...
Last modified: 2008-01-12 15:40:51 UTC
Version: 2.10 What were you doing when the application crashed? crash when opeing program 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.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 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: 112230400 vsize: 112230400 resident: 33447936 share: 26497024 rss: 33447936 rss_rlim: 4294967295 CPU usage: start_time: 1200084361 rtime: 232 utime: 135 stime: 97 cutime:0 cstime: 0 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 -1209215264 (LWP 3117)] [New Thread -1247757424 (LWP 3130)] [New Thread -1218552944 (LWP 3122)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 184982
Thread 1 (Thread -1209215264 (LWP 3117))
----------- .xsession-errors --------------------- (bug-buddy:3134): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (bug-buddy:3134): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (bug-buddy:3134): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (bug-buddy:3134): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (bug-buddy:3134): 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 431459 ***