abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: nautilus component: nautilus crash_function: gdu_device_get_object_path executable: /usr/bin/nautilus kernel: 2.6.35.6-48.fc14.x86_64 package: nautilus-2.32.1-1.fc14 rating: 3 reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1290774505 uid: 500 How to reproduce ----- 1. Compress a folder with the size of 2.2 2. Cancel during compression by force quit 3. Try to open the folder that was being compress
Created attachment 463073 [details] File: backtrace
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Eject Kindle DX 2. Crashes nautilus 3. Kindle ejects sucessfully Comment ----- Ejecting kindle DX crashes nautilus.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.unmounted a usb stick 2. 3.
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.I tried to eject my ebookreader + memory card. First I ejected the memory card after hours of recharging, which went fine. 2.Then I tried to eject the ebookreader 3.Nautilis crashed Comment ----- The ebookreader is basically an elaborate flashdrive
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. copied 20 something files from desktop to HTC Desire device Comment ----- copy, paste, right-click to unmount device, crash report
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Insert Kindle DX 2. Open "Computer" 3. Right click on "Kindle Internal Storage" 4. Select "Eject" Comment ----- Crash while ejecting Kindle DX
Package: nautilus-2.32.1-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.I just right click to safely remove drive(a SD card) 2.Then the bug occur 3.
*** This bug has been marked as a duplicate of bug 650380 ***