GNOME Bugzilla – Bug 451605
crash in Tasks: View an email in an exch...
Last modified: 2007-06-27 13:34:27 UTC
Version: 2.10 What were you doing when the application crashed? View an email in an exchange folder Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Clearlooks Memory status: size: 283480064 vsize: 283480064 resident: 111874048 share: 80191488 rss: 111874048 rss_rlim: 4294967295 CPU usage: start_time: 1182948311 rtime: 7678 utime: 6881 stime: 797 cutime:64 cstime: 62 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 -1208838432 (LWP 20584)] [New Thread -1363174512 (LWP 25417)] [New Thread -1303389296 (LWP 25416)] [New Thread -1269884016 (LWP 20676)] [New Thread -1374585968 (LWP 20650)] [New Thread -1292899440 (LWP 20618)] [New Thread -1210938480 (LWP 20615)] (no debugging symbols found) 0x003ae402 in __kernel_vsyscall ()
+ Trace 144108
Thread 1 (Thread -1208838432 (LWP 20584))
----------- .xsession-errors (17680 sec old) --------------------- bad image index (gnome-panel:2903): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid bad image index (gnome-panel:2903): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid bad image index (gnome-panel:2903): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid bad image index ...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 the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 433922 ***