Bug 675353 - [abrt] nautilus-2.32.2.1-2.fc14: gdu_device_get_object_path: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Summary: [abrt] nautilus-2.32.2.1-2.fc14: gdu_device_get_object_path: Process /usr/bin...
Keywords:
Status: CLOSED DUPLICATE of bug 650380
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:193e33e44ea29f890a8e73b8eaf...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-05 02:12 UTC by Joel Cordero
Modified: 2015-03-03 22:58 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-20 18:36:13 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (28.40 KB, text/plain)
2011-02-05 02:12 UTC, Joel Cordero 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Joel Cordero 2011-02-05 02:12:34 UTC 
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.10-74.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: 1296854224
uid: 500

How to reproduce
-----
1.dont know
2.
3.
Comment 1 Joel Cordero 2011-02-05 02:12:37 UTC 
Created attachment 477156 [details]
File: backtrace
Comment 2 Johan Vervloet 2011-02-16 08:48:13 UTC 
Package: nautilus-2.32.2.1-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Made a bootable usb stick as follows: su -c "dbus-launch --exit-with-session unetbootin"
2. Opened nautilus, right clicked the usb-stick, and clicked 'unmount'
3. Crash
Comment 3 Michael Schwendt 2011-02-20 18:36:13 UTC 

*** This bug has been marked as a duplicate of bug 650380 ***
Note You need to log in before you can comment on or make changes to this bug.