abrt version: 1.1.13 architecture: x86_64 Attached file: backtrace cmdline: nautilus comment: Eject Kindle DX. 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.0-1.fc14 rating: 4 reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1289013711 uid: 500 How to reproduce ----- 1. Insert Kindle DX 2. Eject Kindle DX 3.
Created attachment 458266 [details] File: backtrace
Package: nautilus-2.32.0-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. try to unmount USB drive 2. get crash 3.
*** Bug 654946 has been marked as a duplicate of this bug. ***
Same as: Fedora 13 bug 595402 (gnome-disk-utility)
*** Bug 672288 has been marked as a duplicate of this bug. ***
*** Bug 675353 has been marked as a duplicate of this bug. ***
*** Bug 657546 has been marked as a duplicate of this bug. ***
*** Bug 661897 has been marked as a duplicate of this bug. ***
Package: nautilus-2.32.2.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. No idea - logged in to laptop after waking from sleep 2. 3.
Package: nautilus-2.32.2.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. . Comment ----- Safely remove USB Flash key.
Package: nautilus-2.32.2.1-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.unmounting USB device : sony Tx5 2. 3.
Package: nautilus-2.32.2.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.mounted ntfs drive 2. 3.
Package: nautilus-2.32.2.1-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I just close the Nautilus window 2. 3.
Package: nautilus-2.32.2.1-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Finished using a device which includes two USB drives. 2.Right-clicked and selected 'Safely remove drive' for one of the drives. 3.The drive dismounted, and I was in the process of repeating it for the other drive when the screen went blank for a couple of seconds, and then came back.
Package: nautilus-2.32.2.1-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.exactly the same as yesterday (see above) 2. 3.
Package: nautilus-2.32.2.1-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- I don't know
Package: nautilus-2.32.2.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. have a USB stick with 2 partitions (one VFAT, one luks) 2. write to luks partition 3. use nautilus' umount contextual menu entry on the luks partition (knowing that nautilus umounts both) nautilus crashed this is not reproducible, I do the steps 1-3 quyite often (always grumbling at nautilus unmounting all partitions on the stick, but well that is another story), today it crashed, most days it does not.
Package: nautilus-2.32.2.1-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Selected 'Safely remove drive' for a USB drive of 320GB 2.While that was happening, I selected 'Safely remove drive' for a duplicate backup 3.The first drive disappeared correctly, and then the crash happened.
It was actually a drive of 250GB. The drive that I use for its duplicate is 320GB.
Package: nautilus-2.32.2.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. . Comment ----- "Safely removed" a USB flash key.
Package: nautilus-2.32.2.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Mount (rooted) Samsung Galaxy S with SD Card (eg. both mountpoints are detected and mounted) 2. Unmount the internal SD card with "Safely remove device" 3. Crash!
Package: nautilus-2.32.2.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.just crash 2. 3.
Package: nautilus-2.32.2.1-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.inicia normalmente el sistema y conecto 2 discos duros USB 2.Despues de algunas horas de transferir archvios quedan inactivos los discos 3.al momento de mandar a expulsar con seguridad solo 1 de los 2 discos duros USB se cae Nautilus
Package: nautilus-2.32.2.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I have unmounted the pendrive. Comment ----- I unmounted pendrive with rigth click and choose "unmount drive". Maybe will be helpful info that it was a OCZ ATV 16G pen with NTFS file system, and I just finish to copy the 6.2 GB file on it.
Package: nautilus-2.32.2.1-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.. 2. 3.
Package: nautilus-2.32.2.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Dismounted a USB stick drive from the desktop using the "Safely Remove Drive" option, which in my case does not normally crash Nautilus, but this time it did.
Package: nautilus-2.32.2.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Unmounting volume 2. 3.
Package: nautilus-2.32.2.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. . Comment ----- "Safely removed" a flash usb key with FAT32.
Package: nautilus-2.32.2.1-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Umount Hard Drive(Mobile) 2. 3.
Package: nautilus-2.32.2.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. removed an external USB HD 2. nautilus crashed
Package: nautilus-2.32.2.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I don't know 2. 3.
Package: nautilus-2.32.2.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. . Comment ----- "Safely removed" removeable media.
*** Bug 702731 has been marked as a duplicate of this bug. ***
*** Bug 759901 has been marked as a duplicate of this bug. ***
*** Bug 722343 has been marked as a duplicate of this bug. ***
Clicked "safely remove drive" for USB drive containing 4 mounted partition. (Possibly all open too). backtrace_rating: 4 Package: nautilus-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 578765 [details] File: backtrace
was 'safely removing' a drive that I was not displaying in nautilus backtrace_rating: 4 Package: nautilus-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 581274 [details] File: backtrace
I unmounted USB disk. backtrace_rating: 4 Package: nautilus-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 582482 [details] File: backtrace
I had just created a encryted usb flashdrive. 1 partition encrytped the other not (fat16) After the creation, removed the stick inserted it again for test. Both partition where mounted as expected. I wanted to umount (eject) the non-encryted partition but instead I pressed "safely remove drive" . I have just tried it with eject is also created a core dump. (unecrypted partition) 'safely remove drive' May 21 14:51:52 Big-Brother kernel: [96931.193494] sdd: sdd1 sdd2 May 21 14:51:52 Big-Brother kernel: [96931.196605] sd 8:0:0:0: [sdd] Attached SCSI removable disk May 21 14:52:11 Big-Brother kernel: [96950.792402] EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem May 21 14:52:11 Big-Brother kernel: [96950.807060] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null) May 21 15:01:24 Big-Brother kernel: [97503.188452] nautilus[2819]: segfault at 18 ip 0000003de66197d0 sp 00007fffea643f48 error 4 in libgdu.so.0.0.0[3de6600000+38000] May 21 15:01:24 Big-Brother kernel: [97503.263062] WARNING! power/level is deprecated; use power/control instead May 21 15:01:24 Big-Brother kernel: [97503.323038] usb 1-7: USB disconnect, device number 18 May 21 15:01:28 Big-Brother abrt[20027]: Saved core dump of pid 2819 (/usr/bin/nautilus) to /var/spool/abrt/ccpp-2012-05-21-15:01:24-2819 (100704256 bytes) May 21 15:01:28 Big-Brother abrtd: Directory 'ccpp-2012-05-21-15:01:24-2819' creation detected 'eject' May 21 15:06:47 Big-Brother kernel: [97826.703947] sd 9:0:0:0: [sdd] Attached SCSI removable disk May 21 15:07:05 Big-Brother kernel: [97844.781049] EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem May 21 15:07:05 Big-Brother kernel: [97844.804034] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null) May 21 15:07:58 Big-Brother kernel: [97897.064204] nautilus[20130]: segfault at 18 ip 0000003de66197d0 sp 00007fff73ce84d8 error 4 in libgdu.so.0.0.0[3de6600000+38000] May 21 15:07:58 Big-Brother kernel: [97897.153245] sdd: detected capacity change from 16008609792 to 0 backtrace_rating: 4 Package: nautilus-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Package: nautilus-3.0.2-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- changed folder
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping