Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 595926 - [abrt] crash in mono-core-2.6.1-2.fc13: raise: Process /usr/bin/mono was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in mono-core-2.6.1-2.fc13: raise: Process /usr/bin/mono was kill...
Keywords:
Status: CLOSED DUPLICATE of bug 597666
Alias: None
Product: Fedora
Classification: Fedora
Component: mono
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Xavier Lamien
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:85ca061d3ca289334961b20a153...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-25 22:32 UTC by Sebastian
Modified: 2010-11-09 14:27 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 14:27:31 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (25.51 KB, text/plain)
2010-05-25 22:32 UTC, Sebastian 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Sebastian 2010-05-25 22:32:56 UTC 
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: banshee-1 /usr/lib/banshee-1/Banshee.exe --redirect-log --play-enqueued
comment: I was just closing banshee and mono crashed
component: mono
crash_function: raise
executable: /usr/bin/mono
global_uuid: 85ca061d3ca289334961b20a153f167601592fcc
kernel: 2.6.33.4-95.fc13.i686
package: mono-core-2.6.1-2.fc13
rating: 4
reason: Process /usr/bin/mono was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
How to reproduce: 1. just closed banshee
Comment 1 Sebastian 2010-05-25 22:32:59 UTC 
Created attachment 416577 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 14:27:31 UTC 

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