GNOME Bugzilla – Bug 498828
crash in Tasks: answer an email
Last modified: 2007-11-21 22:42:20 UTC
Version: 2.10 What were you doing when the application crashed? answer an email 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.7-85.fc7 #1 SMP Fri Sep 21 19:53:05 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Bluecurve Memory status: size: 235753472 vsize: 235753472 resident: 91054080 share: 71335936 rss: 91054080 rss_rlim: 4294967295 CPU usage: start_time: 1195541301 rtime: 2827 utime: 2552 stime: 275 cutime:43 cstime: 22 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 -1208863008 (LWP 9141)] [New Thread -1321677936 (LWP 17986)] [New Thread -1354765424 (LWP 9226)] [New Thread -1260700784 (LWP 9191)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 179154
Thread 1 (Thread -1208863008 (LWP 9141))
----------- .xsession-errors (136393 sec old) --------------------- (evolution:9141): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (evolution:9141): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (evolution:9141): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (evolution:9141): 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 458322 ***