Bug 669730 - [abrt] nautilus-2.32.2.1-1.fc14: pid_get_command_line: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Summary: [abrt] nautilus-2.32.2.1-1.fc14: pid_get_command_line: Process /usr/bin/nauti...
Keywords:
Status: CLOSED DUPLICATE of bug 674833
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:75875bb0f0d2cc4ac04504f9f0f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-14 15:04 UTC by ricardoramoscabral
Modified: 2015-03-03 22:57 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-21 15:08:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (60.01 KB, text/plain)
2011-01-14 15:04 UTC, ricardoramoscabral
no flags Details

Description ricardoramoscabral 2011-01-14 15:04:23 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: nautilus
component: nautilus
crash_function: pid_get_command_line
executable: /usr/bin/nautilus
kernel: 2.6.35.10-74.fc14.i686
package: nautilus-2.32.2.1-1.fc14
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1295011786
uid: 500

How to reproduce
-----
1. Safely Remove USB External  HDD
2.
3.

Comment 1 ricardoramoscabral 2011-01-14 15:04:27 UTC
Created attachment 473540 [details]
File: backtrace

Comment 2 Alex 2011-01-18 09:07:17 UTC
Package: nautilus-2.32.2.1-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. logging in after updating PackageKit to 0.6.11-2
2. unmounting another hard disk regularly mounted on /media
3.


Comment
-----
I updated PackageKit as requested from automatic update, but could not unmount another physical disk (that is, I got the same error message as this one). However, I logged out and back in, hoping this would solve the issue, but the folder was still there and when I tried again to unmount, the error message flashed up another time (but the folder stood still: I can work on it, even # umount reports "device is busy" and therefore cannot operate

Comment 3 abrt-bot 2012-03-21 15:08:52 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 #674833, bug #712928

This comment is automatically generated.

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


Note You need to log in before you can comment on or make changes to this bug.