Bug 702731

Summary: [abrt] nautilus-2.32.2.1-2.fc14: gdu_device_get_object_path: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Antoine Martin <antoine>
Component: nautilusAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: alphamike, bugreporter1, bugzilla.redhat, ccecchi, cyberrider, falsedust, handyj, hoffmann, joel.cordero, rbz, rianby64, robert.keersse, spetreolle, stuart, tbzatek, tsmetana, xeddvok7bd7464n2
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:de804728a3dde84a07c22f8b4fb3aa919caa476a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 17:01:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: backtrace
none
File: backtrace none

Description Antoine Martin 2011-05-06 19:10:59 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 31903 bytes
cmdline: nautilus
component: nautilus
Attached file: coredump, 81944576 bytes
crash_function: gdu_device_get_object_path
executable: /usr/bin/nautilus
kernel: 2.6.35.12-90.fc14.x86_64
package: nautilus-2.32.2.1-2.fc14
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1304706765
uid: 500

How to reproduce
-----
1. "Safely remove drive" (USB drive)

Comment 1 Antoine Martin 2011-05-06 19:11:02 UTC
Created attachment 497432 [details]
File: backtrace

Comment 2 John 2011-05-09 15:45:51 UTC
Package: nautilus-2.32.2.1-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Clicked 'Places'
2. Selected Computer
3. Right mouse click on thumbdrive I wanted to remove. 'Safely remove'
4. Crash.

Comment 3 Andres Rios 2011-05-13 11:12:38 UTC
Package: nautilus-2.32.2.1-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Remove USB flash-memory
2. 
3.


Comment
-----
I had at the moment of this error 2 connections by sshfs

Comment 4 Robert Keersse 2011-05-16 04:14:00 UTC
Package: nautilus-2.32.2.1-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.?
2.
3.

Comment 5 Bug Reporter 2011-06-02 12:36:49 UTC
Package: nautilus-2.32.2.1-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. started nautilus as root.
2.
3.

Comment 6 Sylvain Petreolle 2011-06-02 19:57:27 UTC
Package: nautilus-3.0.2-1.fc15
Architecture: i686
OS Release: Fedora release 15 (Lovelock)


Comment
-----
I tried to "safely remove" an USB datapen in Nautilus.

Comment 7 avc4ge28 2011-06-16 15:19:36 UTC
Package: nautilus-3.0.2-1.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)


Comment
-----
this problem happens while installing printer driver

Comment 8 xeddvok7bd7464n2 2011-06-30 21:16:37 UTC
Package: nautilus-3.0.2-1.fc15
Architecture: i686
OS Release: Fedora release 15 (Lovelock)

Comment
-----
* I wanted to "Savely Remove [a] Drive" ('computer:///')
* Nautilus crashed

Comment 9 mkronsteiner 2011-07-09 16:25:10 UTC
Package: nautilus-3.0.2-1.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)

Comment
-----
"safely unmounting" my mp3 player

Comment 10 rbz 2011-08-08 10:42:25 UTC
Package: nautilus-2.32.2.1-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. I had just removed a usb stick, apparently successfully, then I noticed another oddly named top level "device" or file, that I did not recognise, called something like "i7we6ft.iso".

2. Since I didn't recognise it and nautilus seemed unable to show me the content (nothing happened after a double click) and since it was not mounted according to mount, I though I would try "safely remove" to try to get rid of it.

3. Nautilus crashed


Comment
-----
Tried to safely remove (or was it unmount?) a device at the top (computer) level. Nautilus crashed.

In general I find the top level concept a bit confusing - I can never decide for sure what I am looking at. There are devices, some of which are mounted and some not, or? But how can I tell which is which? The already mounted ones should be indicated in some way e.g. via a flag or colour or tone...

Further, if some are just (not yet) mounted devices, why are only these devices shown?
There are a lot of other devices, so why do I only some of them?

IMHO some more context (or some way to easily get more context) would be useful e.g. a hover thingy or a status line showing, for example:
Type: Storage device (device size 32GB)
Vendor: Nokia
Status: Not yet mounted
Connected via: USB Interface (version 3)
Connected since: 8:32
This Device ID last seen: February 13th

Comment 11 falsedust 2011-08-10 14:58:39 UTC
Package: nautilus-3.0.2-1.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)

Comment
-----
Safely removing CF card. I have my CF card from my camera plugged into a front USB port via a card reader.

Comment 12 John 2011-08-18 23:23:29 UTC
Package: nautilus-2.32.2.1-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Click Places -> Computer
2. Right click usb device -> click 'Safely Remove Device'
3.


Comment
-----
Nautilus crashed after doing the above.

Comment 13 Sylvain Petreolle 2011-09-20 17:29:22 UTC
Package: nautilus-3.0.2-1.fc15
Architecture: i686
OS Release: Fedora release 15 (Lovelock)

Comment
-----
I tried to "safely remove" an USB datapen in Nautilus.

Comment 14 Joel Cordero 2011-09-28 23:32:37 UTC
Package: nautilus-2.32.2.1-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.no idea
2.
3.

Comment 15 Dirk Hoffmann 2011-10-15 21:50:48 UTC
Package: nautilus-2.32.2.1-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Mount a partition from a remote server via FTP (in nautilus)
2. Mount two partitions of a local USB disk
3. Try to unmount one of the USB partitions
4. No reaction, then crash.

I do not know, if this is reproducible.

Comment 16 Scott Marshall 2011-11-15 01:21:17 UTC
Package: nautilus-2.32.2.1-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Start Nautilus file browser
2. Right click on an external file system in the left-hand pane.
3. From the desktop, right-click the automount desktop icon for the same file system and choose the "Safely Remove Drive" option.

Comment 17 Stuart D Gathman 2012-01-25 04:32:39 UTC
Open "Computer" from desktop (using gnome fallback mode, nautilus controls desktop option set)
Right click on icon for USB flash drive and select "Safely remove drive"
Crash!
Drive does seems to be unmounted afterward.


backtrace_rating: 4
Package: nautilus-3.2.1-2.fc16
Architecture: i686
OS Release: Fedora release 16 (Verne)

Comment 18 Stuart D Gathman 2012-01-25 04:32:45 UTC
Created attachment 557368 [details]
File: backtrace

Comment 19 Stuart D Gathman 2012-01-25 04:36:05 UTC
Can someone set the version to 16?  This is still not fixed.

Comment 20 Dagan McGregor 2012-03-03 11:36:19 UTC
Was trying to "Safely remove device" on a USB flash drive I had copied files onto

backtrace_rating: 4
Package: nautilus-3.2.1-2.fc16
OS Release: Fedora release 16 (Verne)

Comment 21 Dagan McGregor 2012-03-03 11:36:27 UTC
Created attachment 567271 [details]
File: backtrace

Comment 22 abrt-bot 2012-03-20 17:01:32 UTC
Backtrace analysis found this bug to be similar to bug #650380, closing as duplicate.

Bugs which were found to be similar to this bug: 
  gnome-disk-utility: bug #565320, bug #650380, bug #654946
  nautilus: bug #551675, bug #594969, bug #595089, bug #597292, bug #597990, bug #597992, bug #600421, bug #601257, bug #603570, bug #605758, bug #608498, bug #614052, bug #615663, bug #615730, bug #617819, bug #618833, bug #624112, bug #624835, bug #659559, bug #661897, bug #672288, bug #675353, bug #722343, bug #759901

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 650380 ***