Ubuntu
balazar package

[feisty] when a GL game crashes, I get back to KDM

Bug #114514 reported by Eero Tamminen on 2007-05-13

Affects		Status	Importance	Assigned to	Milestone
	balazar (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Version:
- Kubuntu: Feisty Fawn 7.04

Test-case:
- Start a crashing fullscreen OpenGL game (for example for me Balazar crashes[1])
- Make the game to crash

Expected outcome:
- I get back to KDE desktop (and might have some other problems)

Actual outcome:
- I get back KDM prompt and my session is gone

Session being saved, X server reseted and user notified about that might be in this case best option as OpenGL apps can really mess X server, but I only get back to KDM.

[1] Balazar crash on my MGA G550 produces following output in case that helps:
* Soya * Using 8 bits stencil buffer
* Soya * version 0.12
* Using OpenGL 1.2 Mesa 6.5.2
* - renderer : Mesa DRI G400 20061030 AGP 4x x86/MMX+/3DNow!+/SSE
* - vendor : VA Linux Systems Inc.
* - maximum number of lights : 8
* - maximum number of clip planes : 6
* - maximum number of texture units : 2
* - maximum texture size : 1024 pixels
...
Exception exceptions.OverflowError: 'long int too large to convert to int' in '_soya._Material._pack' ignored
Exception exceptions.OverflowError: 'long int too large to convert to int' in '_soya._Material._pack' ignored
* Tofu * Level level_0_0 147526796 activated !
* Tofu * Player eero login !
python: ../../../../../src/mesa/tnl_dd/t_dd_vb.c:298: mga_interp_extras: Assertion `VB->ColorPtr[1]->stride == 4 * sizeof(GLfloat)' failed.
Aborted (core dumped)

Revision history for this message

Ralf Nieuwenhuijsen (ralf-nieuwenhuijsen) wrote on 2007-09-20:

Seems to be two different issues at play here.
First, balazar shouldn't crash.
Secondly, when it does it should bring your whole xsession down with it.

So, what is your graphics hardware?
Which graphics driver (a binary blob or an opensource variant) are you using?
Are you running compiz?

Is the error reproduceable? If so, how?
Are there things you can do, like turn off compiz that prevent it from happening?

Although the game shouldn't crash, the fact you are booted back into kdm suggest a more dangerous bug is lurking out there...

Revision history for this message

Eero Tamminen (oak-helsinkinet) wrote on 2007-09-20:

glxinfo output Edit (5.9 KiB, text/plain)

> 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.

Revision history for this message

Eero Tamminen (oak-helsinkinet) wrote on 2007-10-21:

I finally had Desktop in state where I can let it freely crash and time to test this again (installed the 20 extra non-main packages required by Balazar etc).

Balazar still crashes, but my Desktop survives now just fine (at least when not using fullscreen), I guess due to the updates/fixes to X server MGA drivers. I.e. this bug can now be moved to Balazar.

For some reason the Balazar window kept black when I started it for the first time. On further runs I can see the window contents. Each times the game crashed after clicking the game window and using keys a little.

After:
* Tofu * Level level_0_0 148967228 activated !
* Tofu * Player eero login !

I get lots of these:
Exception exceptions.OverflowError: 'long int too large to convert to int' in '_soya._Material._pack' ignored

And finally:
python: ../../../../../src/mesa/tnl_dd/t_dd_vb.c:298: mga_interp_extras: Assertion `VB->ColorPtr[1]->stride == 4 * sizeof(GLfloat)' failed.
Aborted (core dumped)

Maybe the game has some unsound assumptions which are not valid on 16-bit displays?

Revision history for this message

Ralf Nieuwenhuijsen (ralf-nieuwenhuijsen) wrote on 2007-10-21:

"Maybe the game has some unsound assumptions which are not valid on 16-bit displays?"

You might be right. At least the bug in xserver, that made it bring down your desktop session too, is gone.
I'm not sure balazar is even maintained at this point.

Revision history for this message

Daniel T Chen (crimsun) wrote on 2008-10-09:

Is this symptom still reproducible in 8.10 beta?

Changed in balazar:
status:	New → Incomplete

Revision history for this message

Jonathan Thomas (echidnaman) wrote on 2008-11-05:

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!