GNOME Bugzilla – Bug 480583
crash in Tasks: The program was receivin...
Last modified: 2007-09-26 17:58:40 UTC
Version: 2.10 What were you doing when the application crashed? The program was receiving POP mail from "pop.google.com" It seemed to be a single e-mail. When the process was going to finish, it failed and this error popped. 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.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks_Cairo-Gull Icon Theme: Fedora Memory status: size: 117055488 vsize: 117055488 resident: 39145472 share: 27643904 rss: 39145472 rss_rlim: 4294967295 CPU usage: start_time: 1190811479 rtime: 195 utime: 133 stime: 62 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 -1208228128 (LWP 3118)] [New Thread -1229980784 (LWP 3129)] [New Thread -1217762416 (LWP 3126)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 165638
Thread 1 (Thread -1208228128 (LWP 3118))
----------- .xsession-errors (33 sec old) --------------------- (evolution:3118): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (evolution:3118): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (evolution:3118): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (evolution:3118): 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 364700 ***