GNOME Bugzilla – Bug 456941
crash in Home Folder:
Last modified: 2007-07-25 13:41:04 UTC
What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Neu Memory status: size: 608645120 vsize: 608645120 resident: 34611200 share: 18522112 rss: 34611200 rss_rlim: 18446744073709551615 CPU usage: start_time: 1184445866 rtime: 570 utime: 369 stime: 201 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496397360 (LWP 14067)] [New Thread 1147169104 (LWP 14087)] (no debugging symbols found) 0x0000003c13cc82e6 in poll () from /lib64/libc.so.6
+ Trace 148043
Thread 2 (Thread 1147169104 (LWP 14087))
----------- .xsession-errors (42788 sec old) --------------------- bad image index (rhythmbox:3350): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid bad image index (rhythmbox:3350): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid bad image index (rhythmbox:3350): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid bad image index ...Too much output, ignoring rest... --------------------------------------------------
*** Bug 456953 has been marked as a duplicate of this bug. ***
*** Bug 456961 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 456131 ***