Created attachment 571826 [details] Output sent to terminal window Description of problem: Sumwars goes through some startup but segfaults before the game is ready to play. Version-Release number of selected component (if applicable): sumwars-0.5.6-5.fc17.x86_64 How reproducible: 100% Steps to Reproduce: 1.sumwars 2. 3. Actual results: Expected results: Additional info:
I will note that sumwars also didn't work on an rv280 (another segfault but preceeding terminal output was a little different) nor an nv28 (assertion failure in the video driver). Though those cards may not be powerful enough to play the game on in practice even if they did work.
Unfortunately I can't reproduce this behaviour. I tested on Intel HD 3000 (Lenovo T420S). I don't have access to any AMD GPUs, I am talking to upstream about this and they do use AMD/ATI cards with FOSS drivers and claim that it works for them. Debugging on your system would help a ton.
That's encouraging news. I thought maybe they were using HLSL shader code or something. I am very likely to be able to be able to get a traceback from my rv280 this weekend. My nv28 has what appears to be a driver problem, so that one won't help. I might be able to grab one from my work machine (rv530), but that that's iffier.
(gdb) where #0 0x000000000059e055 in MainWindow::update (this=0xe1e790, time=8.31999969) at /home/bruno/sumwars-0.5.6/src/gui/mainwindow.cpp:284 #1 0x00000000005a0c7e in updateStartScreen (percent=0.100000001, this=<error reading variable: Cannot access memory at address 0x7fffffffb8e8>) at /home/bruno/sumwars-0.5.6/src/gui/application.cpp:1454 #2 Application::updateStartScreen ( this=<error reading variable: Cannot access memory at address 0x7fffffffb8e8>, this@entry=<error reading variable: Cannot access memory at address 0x7fffffffb948>, percent=0.100000001) at /home/bruno/sumwars-0.5.6/src/gui/application.cpp:1442
As a sanity check, I'll note that I just put f17 on an old laptop and sumwars runs surprisingly well on that.
Odd, seems like some initialisation issue. The texture loading lines from stdout are weird. Texture: _cegui_ogre_0: Loading 1 faces(PF_A8B8G8R8,420x500x1) with hardware generated mipmaps from Image. Internal format is PF_A8R8G8B8,420x500x1. On my PC it says: Texture: _cegui_ogre_0: Loading 1 faces(PF_A8B8G8R8,420x500x1) with 0 generated mipmaps from Image. Internal format is PF_A8R8G8B8,420x500x1. So somehow mipmap generation goes wrong on your computer I guess. Do other Ogre applications work fine? This could be some issue in Ogre's GL render system. The textures also are NonPowerOfTwo but I think all GPUs support that nowadays. If they do not, Ogre has a workaround in place (scales to nearest POT size). Could you also attach ~/.sumwars/*.log?
I did a quick test fo vegastrike and it seemed to work OK on the rv530.
Created attachment 572855 [details] Requested logs
Created attachment 572856 [details] Requested logs
Created attachment 572857 [details] config file
Created attachment 572858 [details] Requested logs
Created attachment 572859 [details] config file
Created attachment 572860 [details] config file
Created attachment 572861 [details] Requested logs
I attached all of the log and config files in .sumwars.
I noticed there is an Ogre update available, and I'll look at trying that out to see if it helps with this issue.
I tried sumwars with ogre 1.7.4 and it is still crashing on the rv280 and rv530. In different places, so it might really be two different driver or mesa bugs.
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.
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.