Bug 622806 - [abrt] crash in supertuxkart-0.6.2-3.fc13: raise: Process /usr/bin/supertuxkart was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in supertuxkart-0.6.2-3.fc13: raise: Process /usr/bin/supertuxka...
Keywords:
Status: CLOSED DUPLICATE of bug 626249
Alias: None
Product: Fedora
Classification: Fedora
Component: supertuxkart
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6102d5af84573885d3ec1dafb80...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-10 13:09 UTC by Barbara
Modified: 2010-11-09 13:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 13:19:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (15.69 KB, text/plain)
2010-08-10 13:09 UTC, Barbara
no flags Details

Description Barbara 2010-08-10 13:09:30 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: supertuxkart --log=file
component: supertuxkart
crash_function: raise
executable: /usr/bin/supertuxkart
global_uuid: 6102d5af84573885d3ec1dafb809182652a5f1d7
kernel: 2.6.33.6-147.2.4.fc13.x86_64
package: supertuxkart-0.6.2-3.fc13
rating: 4
reason: Process /usr/bin/supertuxkart was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. start supertuxkart
2. go to Options->Display
3. press "Increase Resolution" and then Apply resolution
4. you will be asked to confirm resolution change but crash happens

Comment 1 Barbara 2010-08-10 13:09:33 UTC
Created attachment 437871 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 13:19:54 UTC

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

Comment 3 Karel Klíč 2010-11-09 13:19:54 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 #626249.

Sorry for the inconvenience.


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