GNOME Bugzilla – Bug 477114
crash in File Browser: searching some files
Last modified: 2007-09-16 01:16:35 UTC
Version: 2.18.3 What were you doing when the application crashed? searching some files 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.22.5-76.fc7 #1 SMP Thu Aug 30 13:08:59 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Fedora Memory status: size: 550326272 vsize: 550326272 resident: 111988736 share: 19263488 rss: 111988736 rss_rlim: 18446744073709551615 CPU usage: start_time: 1189813744 rtime: 1365 utime: 1211 stime: 154 cutime:0 cstime: 3 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 46912496454704 (LWP 2988)] [New Thread 1136679248 (LWP 18066)] (no debugging symbols found) 0x0000003005cc82e6 in poll () from /lib64/libc.so.6
+ Trace 163030
Thread 2 (Thread 1136679248 (LWP 18066))
----------- .xsession-errors (341 sec old) --------------------- (nm-applet:3018): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (nm-applet:3018): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (nm-applet:3018): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (nautilus:2988): 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 454799 ***