Bug 618029 - [abrt] crash in mono-core-2.6.4-1.fc13: raise: Process /usr/bin/mono was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in mono-core-2.6.4-1.fc13: raise: Process /usr/bin/mono was kill...
Status: CLOSED DUPLICATE of bug 597666
Alias: None
Product: Fedora
Classification: Fedora
Component: mono
Version: 13
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Xavier Lamien
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:c739db9ea52af216065cea0b120...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-25 19:03 UTC by Julian Aloofi
Modified: 2010-11-09 14:29 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-11-09 14:29:16 UTC

Attachments (Terms of Use)
File: backtrace (139.98 KB, text/plain)
2010-07-25 19:03 UTC, Julian Aloofi
no flags Details

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
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.

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