Bug 620158 - [abrt] crash in nautilus-2.30.1-4.fc13: raise: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in nautilus-2.30.1-4.fc13: raise: Process /usr/bin/nautilus was ...
Keywords:
Status: CLOSED DUPLICATE of bug 587508
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ed1151c0d0d15ed46bf7beb150c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-01 11:11 UTC by Rolle
Modified: 2015-03-03 22:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 13:42:30 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (69.39 KB, text/plain)
2010-08-01 11:11 UTC, Rolle 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Rolle 2010-08-01 11:11:29 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: nautilus
component: nautilus
crash_function: raise
executable: /usr/bin/nautilus
global_uuid: ed1151c0d0d15ed46bf7beb150cde781c458c379
kernel: 2.6.33.6-147.fc13.x86_64
package: nautilus-2.30.1-4.fc13
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. I closed nautilus with 2-List-View (F3).
2. During the closing process(?)  it seemed where it is not closed and I clicked in the processbar the nautilus again and then it crashed.
3.
Comment 1 Rolle 2010-08-01 11:11:41 UTC 
Created attachment 435849 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 13:42:30 UTC 

*** This bug has been marked as a duplicate of bug 587508 ***
Comment 3 Karel Klíč 2010-11-09 13:42:30 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 #587508.

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