Bug 893880

Summary: [abrt] bzflag-2.4.2-1.fc18: Process /usr/bin/bzflag was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: dean owensby <dfowensby>
Component: xorg-x11-drv-nouveauAssignee: Nils Philippsen <nphilipp>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: airlied, ajax, bskeggs, jeff, nphilipp, rhbugs
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:3bca5c1024b4c9b023c3a9945f40e01d0575813e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 14:39:16 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
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description dean owensby 2013-01-10 05:30:06 UTC 
Description of problem:
install bzflag 2.4.2
play game
approx 3 minutes into play sigseg occurs

Version-Release number of selected component:
bzflag-2.4.2-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        bzflag
executable:     /usr/bin/bzflag
kernel:         3.7.1-5.fc18.x86_64
remote_result:  NOTFOUND
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 nv50_program_upload_code at nv50_program.c:401
 #3 nv50_program_validate at nv50_shader_state.c:123
 #4 nv50_vertprog_validate at nv50_shader_state.c:152
 #5 nv50_state_validate at nv50_state_validate.c:386
 #6 nv50_draw_vbo at nv50_vbo.c:744
 #7 st_draw_vbo at ../../src/mesa/state_tracker/st_draw.c:265
 #8 vbo_save_playback_vertex_list at ../../src/mesa/vbo/vbo_save_draw.c:323
 #9 ext_opcode_execute at ../../src/mesa/main/dlist.c:619
 #10 execute_list at ../../src/mesa/main/dlist.c:7695
 #11 _mesa_CallList at ../../src/mesa/main/dlist.c:9137
Comment 1 dean owensby 2013-01-10 05:30:11 UTC 
Created attachment 676056 [details]
File: backtrace
Comment 2 dean owensby 2013-01-10 05:30:13 UTC 
Created attachment 676057 [details]
File: cgroup
Comment 3 dean owensby 2013-01-10 05:30:15 UTC 
Created attachment 676058 [details]
File: core_backtrace
Comment 4 dean owensby 2013-01-10 05:30:18 UTC 
Created attachment 676059 [details]
File: dso_list
Comment 5 dean owensby 2013-01-10 05:30:20 UTC 
Created attachment 676060 [details]
File: environ
Comment 6 dean owensby 2013-01-10 05:30:22 UTC 
Created attachment 676061 [details]
File: limits
Comment 7 dean owensby 2013-01-10 05:30:25 UTC 
Created attachment 676062 [details]
File: maps
Comment 8 dean owensby 2013-01-10 05:30:30 UTC 
Created attachment 676063 [details]
File: open_fds
Comment 9 dean owensby 2013-01-10 05:30:37 UTC 
Created attachment 676064 [details]
File: proc_pid_status
Comment 10 dean owensby 2013-01-10 05:30:40 UTC 
Created attachment 676066 [details]
File: var_log_messages
Comment 11 Jeff Makey 2013-01-26 20:12:52 UTC 
This segfault occurred while drawing a tank, which is a very mature part of the BZFlag code and is unlikely to be the culprit.  I suspect that this is a problem with the nouveau driver, although I can't rule out Mesa.

The nouveau driver on F18 with my GeForce 7025 on-board graphics is fast enough that BZFlag is playable on simple maps, but I need the proprietary NVIDIA driver to consistently get at least 30 frames per second on popular maps (which tend to be complicated).  Installing the NVIDIA driver via the kmod-nvidia RPM from the RPM Fusion repo ought to work around this bug.
Comment 12 Fedora End Of Life 2013-12-21 10:17:58 UTC 
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 18'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 2014-02-05 14:39:19 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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