GNOME Bugzilla – Bug 462188
crash in Tasks: abriendo correo
Last modified: 2007-08-01 12:21:23 UTC
Version: 2.10 What were you doing when the application crashed? abriendo correo 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-33.fc7 #1 SMP Mon Jul 23 17:33:07 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 138018816 vsize: 138018816 resident: 48144384 share: 30035968 rss: 48144384 rss_rlim: 4294967295 CPU usage: start_time: 1185898397 rtime: 972 utime: 738 stime: 234 cutime:50 cstime: 21 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 -1208994080 (LWP 6449)] [New Thread -1290986608 (LWP 6511)] [New Thread -1241519216 (LWP 6487)] [New Thread -1229083760 (LWP 6486)] [New Thread -1218593904 (LWP 6482)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 151854
Thread 2 (Thread -1290986608 (LWP 6511))
----------- .xsession-errors (93 sec old) --------------------- bad image index (gnome-system-monitor:6415): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid bad image index (gnome-system-monitor:6415): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid bad image index (gnome-system-monitor:6415): 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 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 461153 ***