GNOME Bugzilla – Bug 470278
crash in Tasks: Opened Evolution and ini...
Last modified: 2007-09-21 18:52:21 UTC
Version: 2.10 What were you doing when the application crashed? Opened Evolution and initiated download of e-mails. 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 188301312 vsize: 188301312 resident: 64389120 share: 56782848 rss: 64389120 rss_rlim: 4294967295 CPU usage: start_time: 1188070264 rtime: 200 utime: 134 stime: 66 cutime:2 cstime: 7 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 -1209080096 (LWP 5503)] [New Thread -1345963120 (LWP 5557)] [New Thread -1261560944 (LWP 5537)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 157888
Thread 1 (Thread -1209080096 (LWP 5503))
----------- .xsession-errors (246 sec old) --------------------- (nautilus:5186): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (gnome-panel:5185): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (nautilus:5186): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (gnome-panel:5185): 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 459761 ***