GNOME Bugzilla – Bug 518335
crash in Tasks: saving a e-mail in conce...
Last modified: 2008-02-24 14:10:08 UTC
Version: 2.10 What were you doing when the application crashed? saving a e-mail in concepts 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 123830272 vsize: 123830272 resident: 45166592 share: 30720000 rss: 45166592 rss_rlim: 4294967295 CPU usage: start_time: 1203810647 rtime: 2240 utime: 2093 stime: 147 cutime:1 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 -1208415504 (LWP 2919)] [New Thread -1311782000 (LWP 3110)] [New Thread -1228833904 (LWP 2973)] [New Thread -1278870640 (LWP 2967)] [New Thread -1217836144 (LWP 2940)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 190244
Thread 5 (Thread -1217836144 (LWP 2940))
----------- .xsession-errors (2298 sec old) --------------------- (nm-applet:2851): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (nm-applet:2851): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (nm-applet:2851): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (nm-applet:2851): 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 405646 ***