Follow-up Comment #6, bug #14770 (project wesnoth):
I found differing behaviour when using different window managers, even with
Debian Unstable's libsdl1.2 (1.2.14-3) installed.
$ uname -a
Linux iniquitous 2.6.32-trunk-686 #1 SMP Thu Dec 24 05:52:30 UTC 2009 i686
GNU/Linux
$ dpkg --get-selections | grep libsdl
libsdl-image1.2 install
libsdl-mixer1.2 install
libsdl-net1.2 install
libsdl-sound1.2 deinstall
libsdl-ttf2.0-0 install
libsdl1.2debian install
libsdl1.2debian-alsa install
To reproduce the issue I would run a window manager, start wesnoth, and click
a button like "Load" or "Tutorial". I did not alter or downgrade my libsdl
installation from the Debian packaged default.
My .xsession starts in openbox, so I would run the alternate window manager
by choosing it under the window managers list in the Debian menu.
I could reproduce this issue in these window managers:
openbox, fluxbox, icewm, fvwm
I couldn't reproduce this issue in these window managers:
9wm, afterstep, twm, windowmaker, wm2
If I started in openbox, switched to windowmaker, and then back to openbox, I
still could reproduce the problem after switching back to openbox and then
starting Wesnoth.
If I started in openbox, switched to windowmaker, then started wesnoth (and
confirmed that as expected I could use the buttons), then switched back to
openbox, I could reproduce the issue with the running Wesnoth while using
openbox.
If I used C-f to make Wesnoth full screen (while using openbox), in full
screen mode I had access to the buttons.
I'm available for other testing if you need it.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?14770>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
