#546064 bzflag-client: aborts when run with no parameters

Package:
bzflag-client
Source:
bzflag
Description:
3D first person tank battle game -- client
Submitter:
Russell Coker
Date:
2015-06-21 13:27:09 UTC
Severity:
normal
#546064#5
Date:
2009-09-11 03:22:59 UTC
From:
To:
I get the following error exit when I run "bzflag".  I don't know whether
there is some command-line parameter I should have given or whether it doesn't
like my X server.

I would be happy to provide more information if you can tell me what you need.

The system is an up to date Lenny system running AMD64 with a recent Intel
graphics chipset.

$ bzflag
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:  148
  Current serial number in output stream:  150
#546064#10
Date:
2009-09-11 04:55:41 UTC
From:
To:
Hey Russell. It's been a while. :)

Try rm -rf $HOME/.bzf

then running again.

You may want to back up that directory and send it to me if this does in
fact fix things.

Can you switch display resolutions in X? We call the xf86 interface to
get a list of display modes during startup and it appears that call is
failing. Perhaps we should handle that case, but it's certainly not the
norm. It found the headers and api when it was built.

It would also be interesting to know what happens if you rebuild the deb
on the same machine.
#546064#15
Date:
2009-09-11 04:55:41 UTC
From:
To:
Hey Russell. It's been a while. :)

Try rm -rf $HOME/.bzf

then running again.

You may want to back up that directory and send it to me if this does in
fact fix things.

Can you switch display resolutions in X? We call the xf86 interface to
get a list of display modes during startup and it appears that call is
failing. Perhaps we should handle that case, but it's certainly not the
norm. It found the headers and api when it was built.

It would also be interesting to know what happens if you rebuild the deb
on the same machine.
#546064#20
Date:
2009-09-11 10:25:01 UTC
From:
To:
Yes.

Done that, it makes no difference at all.

xrandr -s 1024x768
xrandr -s 800x600

The above commands both work as expected, but neither leaves the system in a
state where bzflag will run.

I've tried that, it makes no difference.
#546064#25
Date:
2013-05-29 17:18:43 UTC
From:
To:
tags 546064 moreinfo
thanks

Hi Russell,

This looks identical to this often duplicated bug in Ubuntu[0]. Are you
still able to reproduce it?

Best wishes,
Ryan

[0] https://bugs.launchpad.net/ubuntu/+source/libsdl1.2/+bug/162151
#546064#32
Date:
2015-06-21 13:25:10 UTC
From:
To:
The bug is still repeoducible.

I will now try to make an educated guess, please refrain from taking it
as the ultimate explanation:

I have connected a second monitor, and mirrored my first monitor there
(same screen on both). This results in the largest common solution being
used (which is 1024x768 here). Calling the X interface, however, yields
all available resolutions for each screen, then BZFlag tries to use the
best available resolution from there. However, this mode cannot be set,
because the first usable resolution is the largest one supported by
*both* screens.