full-screen opengl apps crash at start

[rrichter]

Binary package hint: bzflag

ich@ich-desktop:~$ bzflag
X Error of failed request: BadValue (integer parameter out of range for operation)
  Major opcode of failed request: 135 (XFree86-VidModeExtension)
  Minor opcode of failed request: 10 (XF86VidModeSwitchToMode)
  Value in failed request: 0x1a5
  Serial number of failed request: 146
  Current serial number in output stream: 148

System:
Ubuntu LINUX 7.10
Mainboard: Asus P4B533
CPU: Intel Pentium 4 2,53 GHz
RAM: 2x512 MB DDR-SDRAM
HDD: 40 GB 7.200 rpm
GPU: Nvidia Geforce 7800 GS 256 MB AGP4x (nvidia driver installed)

[SneakyWho_am_i (sneakywho-am-i)]

I've had this problem with a bunch of things recently. Games like Battle For Wesnoth which had run previously both in fullscreen and windowed mode, suddenly would be forced to run in only one or the other (naturally, the wrong one). As those other apps failed on the same opcode, I expect that if this is a bug then it is would not be a bzflag bug????? (or maybe two bugs come together, one thing failing and other thing not coping with that failure!?!?....)

I'm on Xubuntu Hardy, with an Athlon XP and an ATI Radeon, with the generic kernel and the proprietary video driver thing.

ANYWAY I have a workaround for it.
In the case of bzflag, I was able to start it with

sneaky@ununtu:~$ bzflag -window

Once I have it running in a window I go to the options menu and test all the available resolutions (remember to press "t" to check that it works, not just enter) - it had been trying to load at 1600 x 1200 - which should work fine... But anyway it runs as it should for me at 1440 x 900. Once you've started it in a window and changed the resolution, I think that you should not see that message again.

Hope this helps...
(If it happens to wesnoth, try deleting ~/.wesnoth/preferences ... should be a text file below your home directory)

[InfoLibre (david-vantyghem)]

I've got the same problem with Mandriva 2008.1 and Kubuntu Hardy. Seems to be a Xorg bug.

david@PC-David:~$ bzflag
X Error of failed request: BadValue (integer parameter out of range for operation)
  Major opcode of failed request: 135 (XFree86-VidModeExtension)
  Minor opcode of failed request: 10 (XF86VidModeSwitchToMode)
  Value in failed request: 0x4e
  Serial number of failed request: 149
  Current serial number in output stream: 151
david@PC-David:~$

[nekapuzer (armloch)]

whenever i shutdown (!!) - through the menu - quake4 or enemy territory: quakewars i get the same error:

Shutting down SDL subsystem
X Error of failed request: BadValue (integer parameter out of range for operation)
  Major opcode of failed request: 135 (XFree86-VidModeExtension)
  Minor opcode of failed request: 10 (XF86VidModeSwitchToMode)
  Value in failed request: 0x3400012
  Serial number of failed request: 185
  Current serial number in output stream: 187

i have an x1900xt with the most recent ATI drivers manually installed.

i believe this too to be a sdl/xorg bug??

[nekapuzer (armloch)]

.. i'm also running ubuntu hardy with latest updates as of today.

[quatrecouleurs (obrecht-joel)]

Hello

Bzflag works (not very well) with :
bzflag -window

Then setting a good window definition in options.

ubuntu hardy, up-to-date, with extra sources.list and compiz on with extra features.

[Yozone Wang (wangyaozh)]

Same problem with Ubuntu 8.10

X Error of failed request: BadValue (integer parameter out of range for operation)
  Major opcode of failed request: 134 (XFree86-VidModeExtension)
  Minor opcode of failed request: 10 (XF86VidModeSwitchToMode)
  Value in failed request: 0x7f
  Serial number of failed request: 181
  Current serial number in output stream: 183

[Tim Riker (timriker)]

This is an X bug. Likely an ATI driver issue. Note that it effects similar full screen OpenGL applications.

[Tim Riker (timriker)]

seeing if I can reassign to ATI driver as it's a driver issue

[Tim Riker (timriker)]

guessing this is an ATI driver issue as it appears to effect all full-screen opengl apps

[Bryce Harrington (bryce)]

How the heck is this a driver issue?!?!?

The information collected so far indicates that the client application is making an invalid x11 protocol call, and the x server is returning an error (legitimately).

More likely, all those games use libsdl, and libsdl is making incorrect X calls.

Try again.

[Dimitrios Symeonidis (azimout)]

assigning to the libsdl1.2 package

[bojo42 (bojo42)]

this can be indeed driver related. in my case i got this problem with the free xorg radeon driver and it's Option "IgnoreEDID" "on". without the option everything works fine, so the driver is triggering this bug.

[Chris (angryfirelord)]

I can confirm this issue as well, but only if I'm using a custom resolution.

For instance, if I use my default resolution (1280x1024), then bzflag works. However, if I adjust it down to 1024x768 in the catalyst control center, then the error appears.

I had another computer with an nvidia card that had the same issue and the way I corrected it was by setting it to 1024x768 in the nvidia settings and then telling it to make and save the xorg.conf file. I suspect what is happening is that SDL is attempting to query the available resolutions in xorg and it's going by what's stored in the default and not by whatever the user was set. A bugzilla report on RedHat seems to confirm this: https://bugzilla.redhat.com/show_bug.cgi?id=426011

To work around this, first set bzflag to a lower resolution in windowed mode:

$ bzflag -window 800x600

Then, go to Options and change the resolution. For me, after I did that, it went to fullscreen. However, I have to do that whenever I start up bzflag.