GNOME Bugzilla – Bug 511500
crash in Tasks: opening photo
Last modified: 2008-01-24 15:15:52 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.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 109543424 vsize: 109543424 resident: 41799680 share: 29085696 rss: 41799680 rss_rlim: 4294967295 CPU usage: start_time: 1201084502 rtime: 1520 utime: 1278 stime: 242 cutime:118 cstime: 20 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 -1208677648 (LWP 4557)] [New Thread -1256952944 (LWP 4636)] [New Thread -1267442800 (LWP 4618)] [New Thread -1277932656 (LWP 4593)] [New Thread -1217430640 (LWP 4565)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 186470
Thread 1 (Thread -1208677648 (LWP 4557))
----------- .xsession-errors (25368 sec old) --------------------- (nautilus:3077): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (nautilus:3077): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (nm-applet:3102): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (nm-applet:3102): 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 ***