Many games (for example Supertux) hang X in ubuntu Hardy Heron (32 and 64bit)

[marco.pallotta]

In my Ubuntu Hardy Heron with Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (with intel_agp) when I play supertux (0.3.1d-0ubuntu1) and many other games, after some minutes, my X-Window hangs and the only way is to ctrl_alt_canc to reboot the system. I think the problem is in the vga driver (bug n. 227051)

I tested this issue with Hardy 32 and 64 bit both.

[marco.pallotta (marco-pallotta)]

I forgot to display my kernel version:
2.6.24-18-generic

[Nathan Handler (nhandler)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at [WWW] https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in supertux.

[marco.pallotta (marco-pallotta)]

The problem is either in supertux 2 or supertux (with opengl enabled). However, as sayd in my first post, I don't know if the issue is only related to supertux packages. In fact I think it's also related to intel vga driver in fact:
- with supertux my system hangs
- with random screen saver enabled some time my system hangs (bug 227051)
- with supertux (version 1, even with opengl disabled) run, when I ibernate my laptop my system hangs (without supertux the ibernation goes ok)

[gerar1995 (gerar1995)]

I have the same problem in a Compaq 6720s. After some time of playing supertux X gets weird. The mouse freezes and the color depth changes.

[marco.pallotta (marco-pallotta)]

I confirmed the bug as commented by gerar1995 on post #7

[marco.pallotta (marco-pallotta)]

I changed the bug description as I discovered that the issue also happens with many other games (and with Hardy 32 bit too).

[Geir Ove Myhr (gomyhr)]

This bug report has been inactive for quite some time and in the meantime Ubuntu has moved along. I hope the reported problem has been resolved in the current version of Ubuntu. If it has not and there are people willing to follow up with information collecting and testing, it is best to file a new bug report with the latest Ubuntu development version (currently 10.04, but soon 10.10), using the ubuntu-bug command if possible. Feel free to mention the bug number of this bug.

We are sorry that we are not always have the capacity to look at all reported bugs in a timely manner. Occationally we have to purge old bug reports where no progress has been made, whether it is due to reporter not being able to respond or lack of manpower on the Ubuntu side, in order to keep our list of "active" bugs current. Sorry for the inconvenience this may cause.

Here are a few tips that will increase the chances that your bug gets priority:
* Read https://wiki.ubuntu.com/X/Reporting
* Browse https://wiki.ubuntu.com/X and see if there is some relevant information for you problem
* Respond quickly to questions from triagers
* Try changing things to see if the behaviour changes, e.g.
  * A new mainline kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D (more information at https://wiki.ubuntu.com/KernelTeam/MainlineBuilds)
  * The xorg-edgers PPA: https://launchpad.net/~xorg-edgers/+archive/ppa
  * Various options in `/etc/X11/xorg.conf` (see `man intel`)
* Browse other bug reports to see if you find a similar one and provide the information that is being asked for there.

[marco.pallotta (marco-pallotta)]

In 10.04 the bug seems to be fixed.