Bug 603491

Summary: [abrt] crash in trackballs-1.1.4-11.fc13: raise: Process /usr/bin/trackballs was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Chris Campbell <campbecg>
Component: trackballsAssignee: Hans de Goede <hdegoede>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: hdegoede
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:b4fb61745773a7b0c21313bc7c285ef556bbb397
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-08 09:18:34 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 Chris Campbell 2010-06-13 14:02:46 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: trackballs
comment: Game crashed at game over
component: trackballs
crash_function: raise
executable: /usr/bin/trackballs
global_uuid: b4fb61745773a7b0c21313bc7c285ef556bbb397
kernel: 2.6.33.5-112.fc13.i686
package: trackballs-1.1.4-11.fc13
rating: 4
reason: Process /usr/bin/trackballs was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Set video to windowed mode, 1024x768
2. Died (game over) in second level, game crashed
3.
Comment 1 Chris Campbell 2010-06-13 14:02:48 UTC 
Created attachment 423635 [details]
File: backtrace
Comment 2 Hans de Goede 2010-11-08 09:18:34 UTC 
Hi,

Thanks for the bug report! And sorry for the slow response. This bug is a duplicate of an already filed bug, closing it as such.

Regards,

Hans

*** This bug has been marked as a duplicate of bug 625225 ***
Comment 3 Hans de Goede 2010-11-08 09:21:28 UTC 
Hi again,

Correction, this bug is a duplicate of a later filed bug rather then of an already filed one. Since I've been tracking this bug so far in this later filed bug I've closed this one as a dup of the later bug report (even though the reality is the other way around).

Regards,

Hans