Bug 712928

Summary: [abrt] nautilus-2.32.2.1-2.fc14: pid_get_command_line: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Michal Pomorski <misieck>
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: ccecchi, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:b762ec58ef3fcb6eb8a07d029ff3ac452898dc81
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-21 15:08:40 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

Description Michal Pomorski 2011-06-13 16:09:45 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 88304 bytes
cmdline: nautilus --sm-client-id 10de29490d19943ecd129017684386605400000067240047 --sm-client-state-file /home/michalp/.config/session-state/nautilus-1307385552.state
comment: Happens quite often, but I didnt really try to reliably reproduce it.
component: nautilus
Attached file: coredump, 314433536 bytes
crash_function: pid_get_command_line
executable: /usr/bin/nautilus
kernel: 2.6.35.13-91.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: 1307980056
uid: 502

How to reproduce
-----
1. Connect a usb mass storage device. (nexus one phone in my case)
2. Copy large amount of small files from one place to another on the same USB device.
3. After its done, click on the eject button in nautilus.
Comment 1 Michal Pomorski 2011-06-13 16:09:49 UTC 
Created attachment 504486 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-21 15:08:40 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 #667006, bug #669730, bug #674833

This comment is automatically generated.

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