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 592088 - [abrt] crash in abuse-0.7.1-4.fc12: raise: Process /usr/bin/abuse was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in abuse-0.7.1-4.fc12: raise: Process /usr/bin/abuse was killed ...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: abuse
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Hans de Goede
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:858238b4b2e07ffdbdc537de8e9...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-13 19:59 UTC by ggoscare
Modified: 2010-06-22 10:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-22 10:17:50 UTC


Attachments (Terms of Use)
File: backtrace (deleted)
2010-05-13 19:59 UTC, ggoscare
no flags Details

Description ggoscare 2010-05-13 19:59:36 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/abuse -fullscreen -datadir /usr/share/fRaBs
component: abuse
crash_function: raise
executable: /usr/bin/abuse
global_uuid: 858238b4b2e07ffdbdc537de8e950926e06c1891
kernel: 2.6.32.11-99.fc12.x86_64
package: abuse-0.7.1-4.fc12
rating: 4
reason: Process /usr/bin/abuse was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

Comment 1 ggoscare 2010-05-13 19:59:38 UTC
Created attachment 413883 [details]
File: backtrace

Comment 2 Hans de Goede 2010-06-22 10:17:50 UTC
Thanks for the report abuse-0.7.1-5 with a fix for this backtrace is on its way to rawhide. As this only happens when restarting a game and not during normal game play I'm not going to issue a Fedora 12 or 13 update for this.


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