Bug 603963 - [abrt] crash in file-roller- raise: Process /usr/bin/file-roller was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in file-roller- raise: Process /usr/bin/file-rol...
Status: CLOSED DUPLICATE of bug 560708
Alias: None
Product: Fedora
Classification: Fedora
Component: file-roller   
(Show other bugs)
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:6db400fcc537269bf08c129f8ab...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-15 02:50 UTC by Chris Maynard
Modified: 2010-11-09 15:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-09 15:09:27 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (36.67 KB, text/plain)
2010-06-15 02:50 UTC, Chris Maynard
no flags Details

Description Chris Maynard 2010-06-15 02:50:54 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: file-roller file:///tmp/spelunky_1_1.zip
comment: Created a directory, then tried to extract into that directory. Second time it worked fine.
component: file-roller
crash_function: raise
executable: /usr/bin/file-roller
global_uuid: 6db400fcc537269bf08c129f8ab8883f44b90211
package: file-roller-
rating: 4
reason: Process /usr/bin/file-roller was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

Comment 1 Chris Maynard 2010-06-15 02:50:57 UTC
Created attachment 424015 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 15:09:27 UTC

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

Comment 3 Karel Klíč 2010-11-09 15:09:27 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 #560708.

Sorry for the inconvenience.

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