> Seems to be two different issues at play here. > First, balazar shouldn't crash.
I've got a good but old graphics card. Maybe it missing features surprised Balazar? Attached is "glxinfo" output. I'm also driving the display at 16-bit. > So, what is your graphics hardware? Matrox G550. > Which graphics driver (a binary blob or an opensource variant) are you using? Open source one, xserver-xorg-video-mga. > Are you running compiz? I'm not running anything requiring Composite. Only thing requiring GL is the games. (Tux racer works fine on the card as does Quake I/II/III, Compiz/Beryl are too slow to be usable.) > Is the error reproduceable? If so, how? Just by starting the game, although I have to admit I haven't tested this for a while. I uninstalled Balazar and have now some application data I don't want to lose, so it will take a while to recheck this. > Are there things you can do, like turn off compiz that prevent it from > happening? Not running the game. :-) I think there was some other similar game (using Soya?) that triggered this also, but it's been a while so I'm not completely sure about this. > Although the game shouldn't crash, the fact you are booted back into kdm > suggest a more dangerous bug is lurking out there... I think it's OpenGL/X one really. There were some (plain 2D) X-crasher mga bugs in Edgy which got fixed in Feisty (basically Debian bugfix imports), so I wouldn't be completely surprised if something else had slipped through Ubuntu QA. ** Attachment added: "glxinfo output" http://launchpadlibrarian.net/9417212/glxinfo.txt -- [feisty] when a GL game crashes, I get back to KDM https://bugs.launchpad.net/bugs/114514 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
