Description of problem: 1 Run the game 2 Start a new, single player game 3 Click the "Start Game" button 4 The game begins to load, the loading bar reaches 100%, and then the game crashes and window closes 5 Moments later I'm alerted by ABRT of this signal 11 error I have experience this same error, on a different process, for other games as well. Version-Release number of selected component: 0ad-0.0.13-1.fc18 Additional info: reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /usr/bin/pyrogenesis crash_function: util_format_read_4f executable: /usr/bin/pyrogenesis kernel: 3.9.4-200.fc18.i686 runlevel: N 5 uid: 1000 xsession_errors: /usr/bin/0ad: line 4: 25058 Segmentation fault (core dumped) LD_LIBRARY_PATH=/usr/lib/0ad /usr/bin/pyrogenesis "$@" Truncated backtrace: Thread no. 1 (10 frames) #1 util_format_read_4f at util/u_format.c:209 #2 nv50_emit_vtxattr at nv50_vbo.c:146 #3 nv50_vertex_arrays_validate at nv50_vbo.c:359 #4 nv50_state_validate at nv50_state_validate.c:394 #5 nv50_draw_vbo at nv50_vbo.c:745 #6 cso_draw_vbo at cso_cache/cso_context.c:1406 #7 st_draw_vbo at ../../src/mesa/state_tracker/st_draw.c:286 #8 vbo_handle_primitive_restart at ../../src/mesa/vbo/vbo_exec_array.c:549 #9 vbo_validated_drawrangeelements at ../../src/mesa/vbo/vbo_exec_array.c:968 #10 vbo_exec_DrawRangeElementsBaseVertex at ../../src/mesa/vbo/vbo_exec_array.c:1076
Created attachment 757037 [details] File: backtrace
Created attachment 757038 [details] File: cgroup
Created attachment 757039 [details] File: core_backtrace
Created attachment 757040 [details] File: dso_list
Created attachment 757041 [details] File: environ
Created attachment 757042 [details] File: limits
Created attachment 757043 [details] File: maps
Created attachment 757044 [details] File: open_fds
Created attachment 757045 [details] File: proc_pid_status
Created attachment 757046 [details] File: var_log_messages
Can you confirm it still happens after updating to latest fedora 18? I have a computer with a nvidia card (rawhide) and another with an intel card (f18/f19) where I test my packages, and noticed that 0ad was broken for some time like your crash in the rawhide computer, but after the latest rawhide update it started working again. Note that the backtrace points to a null function pointer call in/from the nouveau driver.
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.
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.