Bug 896241

Summary: [abrt] supertux-0.3.3-7.fc17: radeon_bo_destroy: Process /usr/bin/supertux2 was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Krešimir Mihalj <kmihalj>
Component: supertuxAssignee: Steven Pritchard <steve>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: steve
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:3fd990fb415bfbb4c1a3c2df09ddd4fb2a798bd5
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 11:04:32 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: environ
none
File: backtrace
none
File: limits
none
File: cgroup
none
File: smolt_data
none
File: executable
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: var_log_messages
none
File: open_fds none

Description Krešimir Mihalj 2013-01-16 21:51:31 UTC 
Version-Release number of selected component:
supertux-0.3.3-7.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        supertux2
crash_function: radeon_bo_destroy
kernel:         3.6.11-1.fc17.i686.PAE

truncated backtrace:
:Thread no. 1 (10 frames)
: #6 radeon_bo_destroy at radeon_drm_bo.c:175
: #7 pb_destroy at pipebuffer/pb_buffer.h:232
: #8 pb_reference at pipebuffer/pb_buffer.h:242
: #9 _pb_cache_buffer_destroy at pipebuffer/pb_bufmgr_cache.c:116
: #10 pb_cache_manager_flush at pipebuffer/pb_bufmgr_cache.c:368
: #11 pb_cache_manager_destroy at pipebuffer/pb_bufmgr_cache.c:383
: #12 radeon_winsys_destroy at radeon_drm_winsys.c:280
: #13 r600_destroy_screen at r600_pipe.c:563
: #14 dri_destroy_screen_helper at dri_screen.c:362
: #15 dri_destroy_screen at dri_screen.c:372
Comment 1 Krešimir Mihalj 2013-01-16 21:51:36 UTC 
Created attachment 679864 [details]
File: environ
Comment 2 Krešimir Mihalj 2013-01-16 21:51:39 UTC 
Created attachment 679865 [details]
File: backtrace
Comment 3 Krešimir Mihalj 2013-01-16 21:51:42 UTC 
Created attachment 679867 [details]
File: limits
Comment 4 Krešimir Mihalj 2013-01-16 21:51:44 UTC 
Created attachment 679869 [details]
File: cgroup
Comment 5 Krešimir Mihalj 2013-01-16 21:51:47 UTC 
Created attachment 679871 [details]
File: smolt_data
Comment 6 Krešimir Mihalj 2013-01-16 21:51:51 UTC 
Created attachment 679874 [details]
File: executable
Comment 7 Krešimir Mihalj 2013-01-16 21:51:57 UTC 
Created attachment 679875 [details]
File: maps
Comment 8 Krešimir Mihalj 2013-01-16 21:52:06 UTC 
Created attachment 679876 [details]
File: dso_list
Comment 9 Krešimir Mihalj 2013-01-16 21:52:09 UTC 
Created attachment 679877 [details]
File: proc_pid_status
Comment 10 Krešimir Mihalj 2013-01-16 21:52:15 UTC 
Created attachment 679878 [details]
File: var_log_messages
Comment 11 Krešimir Mihalj 2013-01-16 21:52:17 UTC 
Created attachment 679879 [details]
File: open_fds
Comment 12 Fedora End Of Life 2013-07-04 03:28:59 UTC 
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 13 Fedora End Of Life 2013-08-01 11:04:36 UTC 
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.