Bug 552432 – [abrt] crash detected in raidem-0.3.1-11.fc12

Bug 552432 - [abrt] crash detected in raidem-0.3.1-11.fc12

Summary:	[abrt] crash detected in raidem-0.3.1-11.fc12

Status:	CLOSED INSUFFICIENT_DATA

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	raidem (Show other bugs)
Sub Component:
Version:	12
Hardware:	x86_64 Linux

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Xavier Lamien
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:	abrt_hash:509ea68cfce501d377078bd9588...
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2010-01-04 21:18 EST by Jean Reis
Modified:	2010-02-24 05:22 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2010-02-24 05:22:10 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
File: backtrace (2.92 KB, text/plain) 2010-01-04 21:18 EST, Jean Reis	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Jean Reis 2010-01-04 21:18:28 EST

abrt 1.0.0 detected a crash.

How to reproduce
-----
1.Start Game
2. For some reason, the game is constantly receiving an "Up" key-press, as if the key was stuck (while no key was being pressed)
3. Attempts at quiting the game caused the crash


Attached file: backtrace
cmdline: raidem
component: raidem
executable: /usr/bin/raidem
kernel: 2.6.31.9-174.fc12.x86_64
package: raidem-0.3.1-11.fc12
rating: 3
reason: Process was terminated by signal 6

Comment 1 Jean Reis 2010-01-04 21:18:30 EST

Created attachment 381684 [details]
File: backtrace

Comment 2 Karel Klíč 2010-02-24 05:22:10 EST

This bug appears to have been filled using a buggy version of ABRT, because
it contains unusable backtrace. Sorry for the inconvenience.

Closing as INSUFFICIENT_DATA.

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