GNOME Bugzilla – Bug 509442
crash in Open Folder: opened my USB device and...
Last modified: 2008-01-14 23:52:01 UTC
Version: 2.18.3 What were you doing when the application crashed? opened my USB device and wanted to format it Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: SphereCrystal Icon Theme: Neu Memory status: size: 78315520 vsize: 78315520 resident: 28717056 share: 15929344 rss: 28717056 rss_rlim: 4294967295 CPU usage: start_time: 1200334459 rtime: 856 utime: 803 stime: 53 cutime:1 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 "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6da16b0 (LWP 3993)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 185322
Thread 1 (Thread 0xb6da16b0 (LWP 3993))
----------- .xsession-errors (21 sec old) --------------------- ** Message: volume = 0 ** gg_ping(0x83c56b8); ** gg_send_packet(0x83c56b8, 0x08, ...) // gg_send_packet(0x08) 08 00 00 00 00 00 00 00 ** Message: Hit unexpected error "Directory not empty" while doing a file operation. ** Message: Hit unexpected error "Directory not empty" while doing a file operation. ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** gg_ping(0x83c56b8); ** gg_send_packet(0x83c56b8, 0x08, ...) // gg_send_packet(0x08) 08 00 00 00 00 00 00 00 --------------------------------------------------
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 355018 ***