Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 591917 - [abrt] crash in emesene-1.6-1.fc12: raise: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in emesene-1.6-1.fc12: raise: Process /usr/bin/python was killed...
Status: CLOSED DUPLICATE of bug 561843
Alias: None
Product: Fedora
Classification: Fedora
Component: emesene
Version: 12
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Itamar Reis Peixoto
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:46473b7cdab5e373090004644fe...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-13 13:36 UTC by Daniel Vilha
Modified: 2010-05-24 15:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-05-24 15:04:39 UTC

Attachments (Terms of Use)
File: backtrace (deleted)
2010-05-13 13:37 UTC, Daniel Vilha
no flags Details

Description Daniel Vilha 2010-05-13 13:36:54 UTC
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: python /usr/share/emesene/emesene
component: emesene
crash_function: raise
executable: /usr/bin/python
global_uuid: 46473b7cdab5e373090004644fe71dcdacd2ba70
package: emesene-1.6-1.fc12
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

Comment 1 Daniel Vilha 2010-05-13 13:37:04 UTC
Created attachment 413764 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-24 15:04:39 UTC

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

Comment 3 Karel Klíč 2010-05-24 15:04:39 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 #561843.

Sorry for the inconvenience.

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