Bug 585749 - [abrt] crash in nautilus-2.28.4-2.fc12: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in nautilus-2.28.4-2.fc12: Process /usr/bin/nautilus was killed ...
Keywords:
Status: CLOSED DUPLICATE of bug 572977
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b3cb04ece5a56195b71d392787d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-25 22:07 UTC by sho.shimauchi
Modified: 2015-03-03 22:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-25 09:41:31 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (24.24 KB, text/plain)
2010-04-25 22:07 UTC, sho.shimauchi 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description sho.shimauchi 2010-04-25 22:07:55 UTC 
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: nautilus
component: nautilus
executable: /usr/bin/nautilus
global_uuid: b3cb04ece5a56195b71d392787d8f7e2b544624c
kernel: 2.6.32.11-105.fc12.i686.PAE
package: nautilus-2.28.4-2.fc12
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. move hundreds of files(700MB) to external USB Storage with Ctrl+X + Ctrl+V
2. when file move completed, it crashed immediately.
3. no file corruption occured.
Comment 1 sho.shimauchi 2010-04-25 22:07:57 UTC 
Created attachment 409019 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 09:41:31 UTC 

*** This bug has been marked as a duplicate of bug 572977 ***
Comment 3 Karel Klíč 2010-05-25 09:41:31 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #572977.

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