GNOME Bugzilla – Bug 517799
crash in Tasks: Just opened Evolution
Last modified: 2008-02-21 12:35:44 UTC
Version: 2.10 What were you doing when the application crashed? Just opened Evolution Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 156172288 vsize: 156172288 resident: 35205120 share: 26890240 rss: 35205120 rss_rlim: 4294967295 CPU usage: start_time: 1203566872 rtime: 134 utime: 87 stime: 47 cutime:0 cstime: 2 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 -1208998176 (LWP 2933)] [New Thread -1292915824 (LWP 2992)] [New Thread -1311130736 (LWP 2987)] [New Thread -1282425968 (LWP 2961)] [New Thread -1271936112 (LWP 2960)] [New Thread -1240466544 (LWP 2956)] [New Thread -1217815664 (LWP 2954)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 189935
Thread 1 (Thread -1208998176 (LWP 2933))
----------- .xsession-errors (9 sec old) --------------------- (evolution:2933): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (evolution:2933): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (evolution:2933): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (evolution:2933): 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 ***
*** This bug has been marked as a duplicate of 431459 ***