Bug 618029

Summary: [abrt] crash in mono-core-2.6.4-1.fc13: raise: Process /usr/bin/mono was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Julian Aloofi <julian.fedora>
Component: monoAssignee: Xavier Lamien <lxtnow>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: chkr, itamar, lxtnow, paul
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:c739db9ea52af216065cea0b1202a7c1e71db75f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-09 14:29:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Julian Aloofi 2010-07-25 19:03:22 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: banshee-1 /usr/lib/banshee-1/Banshee.exe --redirect-log --play-enqueued
comment: I just played a song in Banshee, then it switched to the next song and immediately crashed. It played several songs before. It's not possible to reproduce this bug, but it happens from time to time.
component: mono
crash_function: raise
executable: /usr/bin/mono
global_uuid: c739db9ea52af216065cea0b1202a7c1e71db75f
kernel: 2.6.33.6-147.fc13.i686
package: mono-core-2.6.4-1.fc13
rating: 3
reason: Process /usr/bin/mono was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Play a song in Banshee
2. Wait for the next song to start
Comment 1 Julian Aloofi 2010-07-25 19:03:25 UTC 
Created attachment 434274 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 14:29:16 UTC 

*** This bug has been marked as a duplicate of bug 597666 ***
Comment 3 Karel Klíč 2010-11-09 14:29:16 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 #597666.

Sorry for the inconvenience.