URL:
<http://gna.org/bugs/?24695>
Summary: If resolution is set too high, wesnoth does not
lauch
Project: Battle for Wesnoth
Submitted by: bjr
Submitted on: Tue 24 May 2016 09:06:40 PM UTC
Category: Bug
Severity: 2 - Minor
Priority: 5 - Normal
Item Group: User Interface
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: 1.12.6
Operating System: Fedora
_______________________________________________________
Details:
I had Wesnoth installed on a machine running Fedora 23 (wesnoth installed
through the system package manager) that was connected to a 2560x1600 monitor,
so I set the resolution to 2560x1600 using Wesnoth's GUI. Recently, I moved
the machine to a different monitor that doesn't support resolutions that high
and attempted to launch Wesnoth, but nothing happened. I then ran "wesnoth"
from the command line and I got the following output:
$ wesnoth
Battle for Wesnoth v1.12.5
Started on Tue May 24 16:56:01 2016
Data directory: /usr/share/wesnoth
User configuration directory: /home/bjr/.config/wesnoth
User data directory: /home/bjr/.local/share/wesnoth/1.12
Cache directory: /home/bjr/.cache/wesnoth
Checking video mode: 2560x1600x32...
setting mode to 2560x1600x32
required video mode, 2560x1600x32 is not supported
could not initialize display
It'd be nice if, when wesnoth detects the resolution settings were broken and
defaulted to a much lower resolution (the lowest supported by the system?)
rather than refusing to launch, thus allowing the user to use the GUI for
changing graphics settings to adjust it.
I did open the configuration (~/.config/wesnoth/preferences) to take a look at
changing the video mode, but I found the following settings:
xresolution=2560
xwindowsize=2556
yresolution=1600
ywindowsize=1546
It *looks* like {x,y}resolution - 4 = {x,y}windowsize, but I'm not sure how
this is computed and I'd prefer not to mess with it by hand if I didn't have
to. I could also, of course, get rid of that configuration file and generate a
new one from scratch, but that's less than ideal.
So this is work-aroundable but I figured it might be worth filing a bug
anyway?
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?24695>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
