Bug 667006

Summary: [abrt] nautilus-2.32.2-1.fc14: pid_get_command_line: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Alex <a.delachenal>
Component: nautilusAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: ccecchi, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:eb70fa11ebbd3ab3d2ce9f91eb3a0250b34e3f88
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-21 15:09:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Alex 2011-01-04 03:16:16 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: nautilus
comment: I just plugged in a USB pen to copy a few files from another disk (regularly mounted on /media), then unplugged it and tried to unmount the /media disk: then flashed the CRASH alert
component: nautilus
crash_function: pid_get_command_line
executable: /usr/bin/nautilus
kernel: 2.6.35.10-74.fc14.x86_64
package: nautilus-2.32.2-1.fc14
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1294108995
uid: 500

How to reproduce
-----
1. coping files
2. unmount USB pen
3. unmount hard disk

Comment 1 Alex 2011-01-04 03:16:20 UTC
Created attachment 471584 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-21 15:09:01 UTC
Backtrace analysis found this bug to be similar to bug #674833, closing as duplicate.

Bugs which were found to be similar to this bug: bug #611737, bug #620498, bug #628195, bug #652962, bug #655540, bug #669730, bug #674833, bug #712928

This comment is automatically generated.

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