GNOME Bugzilla – Bug 499136
crash in Tasks: Opening images received ...
Last modified: 2007-11-23 21:21:09 UTC
Version: 2.10 What were you doing when the application crashed? Opening images received in Firefox and being viewed in image viewer. 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.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 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: 156737536 vsize: 156737536 resident: 59678720 share: 27783168 rss: 59678720 rss_rlim: 4294967295 CPU usage: start_time: 1195811269 rtime: 4069 utime: 3584 stime: 485 cutime:119 cstime: 29 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 -1208522000 (LWP 3255)] [New Thread -1256797296 (LWP 3348)] [New Thread -1246307440 (LWP 3304)] [New Thread -1217274992 (LWP 3263)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 179348
Thread 1 (Thread -1208522000 (LWP 3255))
----------- .xsession-errors (2391 sec old) --------------------- (nm-applet:3084): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (nm-applet:3084): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (nm-applet:3084): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (nm-applet:3084): 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 ***