Bug 592106

Summary: [abrt] crash in mono-core-2.4.3.1-1.fc12: raise: Process /usr/bin/mono was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Alfred Reaud <alreaud>
Component: monoAssignee: Xavier Lamien <lxtnow>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: chkr, itamar, lxtnow, paul
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:1ab152b4302577d8e4cb8041ce825e7a097bbfdb
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-25 10:42:24 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 Alfred Reaud 2010-05-13 21:01:58 UTC 
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: mono /usr/lib/gnome-do/Do.exe
component: mono
crash_function: raise
executable: /usr/bin/mono
global_uuid: 1ab152b4302577d8e4cb8041ce825e7a097bbfdb
kernel: 2.6.32.11-99.fc12.i686
package: mono-core-2.4.3.1-1.fc12
rating: 3
reason: Process /usr/bin/mono was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

comment
-----
This has occurred since it auto installed. I don't recall asking for it's installation, but it appeared after a regular yum upgrade. 

The system is a VMware virtual machine running in Windows XP, if that has any bearing.

How to reproduce
-----
1. Log in to user account.
2. Quit gnome-do manually via menu at right top corner of window.
3. Wait about 15 sec to 1 min and the crash is reported.
Comment 1 Alfred Reaud 2010-05-13 21:02:00 UTC 
Created attachment 413894 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 10:42:24 UTC 

*** This bug has been marked as a duplicate of bug 587203 ***
Comment 3 Karel Klíč 2010-05-25 10:42:24 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 #587203.

Sorry for the inconvenience.