GNOME Bugzilla – Bug 520217
crash in Tasks: opening photo
Last modified: 2008-03-06 14:46:19 UTC
Version: 2.10 What were you doing when the application crashed? opening photo 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: 109420544 vsize: 109420544 resident: 40964096 share: 27250688 rss: 40964096 rss_rlim: 4294967295 CPU usage: start_time: 1204594212 rtime: 1977 utime: 1792 stime: 185 cutime:122 cstime: 35 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 -1209148688 (LWP 3255)] [New Thread -1246934128 (LWP 3363)] [New Thread -1267913840 (LWP 3290)] [New Thread -1217901680 (LWP 3263)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 191216
Thread 1 (Thread -1209148688 (LWP 3255))
----------- .xsession-errors (996 sec old) --------------------- (gnome-panel:3056): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (gnome-panel:3056): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (nm-applet:3103): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (nm-applet:3103): 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 467763 ***