Bug 611742 - [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...
Keywords:
Status: CLOSED DUPLICATE of bug 597666
Alias: None
Product: Fedora
Classification: Fedora
Component: mono
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Xavier Lamien
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:36e23f330581b64942c8c9a6d00...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-06 10:31 UTC by Orod Moeini
Modified: 2010-11-09 14:28 UTC (History)
4 users (show)

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


Attachments (Terms of Use)
File: backtrace (64.36 KB, text/plain)
2010-07-06 10:31 UTC, Orod Moeini
no flags Details

Description Orod Moeini 2010-07-06 10:31:24 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: mono /usr/lib64/gnome-do/Do.exe
comment: Probably the crash is due to the application or its plugins not being completely loaded and hence crashed
component: mono
crash_function: raise
executable: /usr/bin/mono
global_uuid: 36e23f330581b64942c8c9a6d006620c9cd60447
kernel: 2.6.33.5-124.fc13.x86_64
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. Opening gnome-do dialoge to search for applications after login
2. The dialog remained unresponsive for a few seconds before crashing
3.

Comment 1 Orod Moeini 2010-07-06 10:31:29 UTC
Created attachment 429736 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 14:28:52 UTC

*** This bug has been marked as a duplicate of bug 597666 ***

Comment 3 Karel Klíč 2010-11-09 14:28:52 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.