Bug 616664 - [abrt] crash in asunder-1.9.3-1.fc13: Process /usr/bin/asunder was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in asunder-1.9.3-1.fc13: Process /usr/bin/asunder was killed by ...
Status: CLOSED DUPLICATE of bug 616663
Alias: None
Product: Fedora
Classification: Fedora
Component: asunder (Show other bugs)
(Show other bugs)
Version: 13
Hardware: i686 Linux
low
medium
Target Milestone: ---
Assignee: Marcin Zajaczkowski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:37f36eeba36b764901b24722220...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-21 05:31 UTC by Carlos Islas
Modified: 2010-08-29 19:21 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-08-29 19:21:13 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (26.80 KB, text/plain)
2010-07-21 05:31 UTC, Carlos Islas 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Carlos Islas 2010-07-21 05:31:10 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: asunder
comment: I was just ripping a CD with the Asunder, then suddenly it stopped encoding, just terminate the program via the process monitor.
component: asunder
crash_function: IA__g_type_check_instance_cast
executable: /usr/bin/asunder
global_uuid: 37f36eeba36b764901b24722220ed3ae8a6e0edd
kernel: 2.6.33.3-85.fc13.i686.PAE
package: asunder-1.9.3-1.fc13
rating: 4
reason: Process /usr/bin/asunder was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. 
2.
3.
Comment 1 Carlos Islas 2010-07-21 05:31:13 UTC 
Created attachment 433300 [details]
File: backtrace
Comment 2 Marcin Zajaczkowski 2010-08-29 19:21:13 UTC 

*** This bug has been marked as a duplicate of bug 616663 ***
Note You need to log in before you can comment on or make changes to this bug.