GNOME Bugzilla – Bug 473407
crash in Open Folder: searching for a file
Last modified: 2007-09-05 15:34:39 UTC
Version: 2.18.3 What were you doing when the application crashed? searching for a file 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 85180416 vsize: 85180416 resident: 31834112 share: 21065728 rss: 31834112 rss_rlim: 4294967295 CPU usage: start_time: 1188658381 rtime: 4302 utime: 3867 stime: 435 cutime:51 cstime: 50 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (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 -1208781088 (LWP 2127)] [New Thread -1231860848 (LWP 21244)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 160268
Thread 2 (Thread -1231860848 (LWP 21244))
----------- .xsession-errors (291 sec old) --------------------- expr: syntax error expr: syntax error expr: syntax error expr: syntax error expr: syntax error expr: syntax error expr: syntax error expr: syntax error expr: syntax error Message: alsa mixer timed out could not load face 'file:///home/keith/Shared/Super%20Nintendo%20Roms/Aero%20the%20Acro-Bat%202': unknown file format could not load face 'file:///home/keith/Shared/Super%20Nintendo%20Roms/Art%20of%20Fighting': unknown file format could not load face 'file:///home/keith/Shared/Super%20Nintendo%20Roms/Bassins'%20Black%20Bass%20Fishing%20with%20Hank%20Parker': unknown file format ...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 ***