GNOME Bugzilla – Bug 493637
crash in Open Folder: Closing Nautilus
Last modified: 2007-11-05 09:02:44 UTC
Version: 2.18.3 What were you doing when the application crashed? Closing Nautilus 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.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 154865664 vsize: 154865664 resident: 60923904 share: 34836480 rss: 60923904 rss_rlim: 4294967295 CPU usage: start_time: 1194211403 rtime: 19257 utime: 17205 stime: 2052 cutime:19966 cstime: 1273 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 -1208351008 (LWP 2940)] [New Thread -1317745776 (LWP 31710)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 175326
Thread 1 (Thread -1208351008 (LWP 2940))
----------- .xsession-errors (20787 sec old) --------------------- [mp3 @ 0x881a070]Header missing skipping one byte. [mp3 @ 0x881a070]Header missing skipping one byte. [mp3 @ 0x881a070]Header missing skipping one byte. [mp3 @ 0x881a070]Header missing skipping one byte. [mp3 @ 0x881a070]Header missing skipping one byte. [mp3 @ 0x881a070]Header missing skipping one byte. [mp3 @ 0x881a070]Header missing skipping one byte. [mp3 @ 0x881a070]Header missing skipping one byte. [mp3 @ 0x881a070]Header missing skipping one byte. [mp3 @ 0x881a070]Header missing skipping one byte. [mp3 @ 0x881a070]Header missing skipping one byte. [mp3 @ 0x881a070]Header missing skipping one byte. [mp3 @ 0x881a070]Header missing skipping one byte. [mp3 @ 0x881a070]Heade ...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 356672 ***