Bug 587426

Summary: [abrt] crash in ballz-1.0.1-3.fc12: Process /usr/bin/ballz was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: armando.fella
Component: ballzAssignee: Hans de Goede <hdegoede>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: beuc, hdegoede
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:5abe67865f123ef9a118456419fae506ae5c4d09
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-22 10:31:09 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 armando.fella 2010-04-29 21:08:30 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/ballz
component: ballz
executable: /usr/bin/ballz
global_uuid: 5abe67865f123ef9a118456419fae506ae5c4d09
kernel: 2.6.32.11-99.fc12.x86_64
package: ballz-1.0.1-3.fc12
rating: 4
reason: Process /usr/bin/ballz was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
Comment 1 armando.fella 2010-04-29 21:08:32 UTC 
Created attachment 410233 [details]
File: backtrace
Comment 2 Hans de Goede 2010-06-22 10:31:09 UTC 
Hi,

Thanks for the bug report.

Looking at the backtrace you send a sigterm (signal 15) to ballz in some way (maybe you closed the terminal from which you started it, or you were logging out?), which got intercepted by allegro (the gaming library ballz) uses and then turned into an abort which got intercepted by abrt.

Doing an abort is allegro's standard behaviour when an allegro using game is not exited cleanly, so I don't consider this a bug.

Regards,

Hans