GNOME Bugzilla – Bug 499978
crash in Open Folder: I was looking for a tras...
Last modified: 2007-11-27 20:12:11 UTC
Version: 2.18.3 What were you doing when the application crashed? I was looking for a trash folder or file. Attempting to locate deleted files that are not in the trash folder but are still in the hard drive for unknown reasons. I was not doing anything else during the search. I was watching tv while it searched. 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: Enforcing Accessibility: Disabled GTK+ Theme: Gorilla Icon Theme: Gorilla Memory status: size: 163770368 vsize: 163770368 resident: 45228032 share: 28360704 rss: 45228032 rss_rlim: 4294967295 CPU usage: start_time: 1196162076 rtime: 3097 utime: 1628 stime: 1469 cutime:1741 cstime: 272 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 -1208727840 (LWP 3190)] [New Thread -1319806064 (LWP 8666)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 179825
Thread 2 (Thread -1319806064 (LWP 8666))
----------- .xsession-errors (25 sec old) --------------------- sense key: NOT READY (2) asc: 3a ascq: 2 (K3bDevice::Device) /dev/scd0: READ 10 failed! (K3bDevice::ScsiCommand) failed: command: READ (10) (28) errorcode: 70 sense key: NOT READY (2) asc: 3a ascq: 2 (K3bDevice::Device) /dev/scd0: READ 10 failed! removing udi /org/freedesktop/Hal/devices/volume_empty_dvd_plus_r ICE default IO error handler doing an exit(), pid = 8516, errno = 0 (nautilus:3190): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed --------------------------------------------------
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 ***