bugBattle for Wesnoth - Bugs: bug #20193, wesnoth does not start fullscreen...

Show feedback again

bug #20193: wesnoth does not start fullscreen with wrong resolution set

Submitted by:  Piotr Suwara <peterdes>
Submitted on:  Sat Sep 22 15:55:01 2012  
Category: BugSeverity: 5 - Blocker
Priority: 5 - NormalItem Group: User Interface
Status: FixedPrivacy: Public
Assigned to: Andreas Löf <aginor>Open/Closed: Closed
Release: 1.10.4Operating System: Arch Linux

Add a New Comment (Rich MarkupRich Markup):

You are not logged in

Please log in, so followups can be emailed to you.


(Jump to the original submission Jump to the original submission)

Wed Feb 24 08:58:13 2016, comment #6:

Marking as fixed then.

Andreas Löf <aginor>
Project MemberIn charge of this item.
Wed Dec 30 11:30:48 2015, comment #5:

Vultraz has confirmed it as fixed with SDL2 since we use native desktop resolution for full screen.

Andreas Löf <aginor>
Project MemberIn charge of this item.
Tue Sep 22 13:19:00 2015, comment #4:

SDL2 build might not be fully ready yet, but I'm guessing this one is fixed when it is? Building with SDL2, full-screen mode seems to always run at my monitor's native resolution regardless of what I have set in my preferences file. Building with SDL1.2, I get a scaled image in full-screen mode when preferences is set to something less than the native resolution. Only when preferences is set to something greater than the native resolution does the game appear to not start at all (presumably crashes before a window is even generated), and the stderr.txt exhibits what peterdes describes.

The above is from testing in Windows 7.

Wedge009 <wedge009>
Project Member
Mon Apr 20 03:38:04 2015, comment #3:

Marking as Confirmed since SDL_gpu/SDL 2 support in master is not production-ready yet.

Ignacio R. Morelle <shadowmaster>
Project Administrator
Mon Jun 16 18:12:24 2014, comment #2:

Detection is possible in SDL2 and is in the master branch. It will be present in 1.13.0

Alexander van Gessel <ai0867>
Project Member
Mon Jan 20 03:51:14 2014, comment #1:

I've implemented option 1 in 38df70d25ff0.

Actually trying to detect things may also make sense though.

Alexander van Gessel <ai0867>
Project Member
Sat Sep 22 15:55:01 2012, original submission:

Steps to reproduce:
1. Set the xresolution and yresolution to some arbitrary numbers, f.ex. 1920x1080.
2. Let me have a 1280x1024 screen (different resolution than the above) and start wesnoth in fullscreen mode (either with a --fullscreen option or with the fullscreen set in preferences).
3. Wesnoth crashes (exits with error code 1) with the following command-line messages:
Checking video mode: 1920x1080x32...
setting mode to 1920x1080x32
required video mode, 1920x1080x32 is not supported
could not initialize display

I have attached a log of
wesnoth -f --log-debug=all > wesnoth.log 2>&1

One may repair it by setting proper xresolution and yresolution in the preferences file, but (as I guess) a usual user should never be forced to edit it manually. If fullscreen is set in the preferences (either by default or by user using another resolution earlier), then one is not able to launch wesnoth just by running "wesnoth".

Possible solutions:
1. Wesnoth may try to go windowed mode after failing to run fullscreen.
2. Wesnoth may ask about the resolution if it encounters any problems (indeed it complains about resolutions when switching from windowed to fullscreen mode with the resolutions as mentionet above).
3. Wesnoth may try to guess the proper resolution for fullscreen mode.

What is more, wesnoth may ask user to choose the proper resolution when encountering any problems changing from windowed to fullscreen mode.

I have not encountered this problem on Fedora Linux or Windows - on these, wesnoth running in a bad resolution is just scaled (ugly!). It may be a problem with SDL, but I think that this is not a bug of SDL that it does not run in an inproper mode. Moreover, if(failed) run_windowed(); is... simple and elegant, I guess?

Piotr Suwara <peterdes>


(Note: upload size limit is set to 1024 kB, after insertion of the required escape characters.)

Attach File(s):

Attached Files
file #16599:  wesnoth.log added by peterdes (12kB - application/octet-stream - I attach command line output of wesnoth.)


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -unavailable- added by vultraz (Updated the item)
  • -unavailable- added by aginor (Updated the item)
  • -unavailable- added by wedge009 (Posted a comment)
  • -unavailable- added by ai0867 (Posted a comment)
  • -unavailable- added by shadowmaster (Updated the item)
  • -unavailable- added by peterdes (Submitted the item)

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.


    Error: not logged in



    Follow 9 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Sat Mar 5 13:12:04 2016vultrazOpen/ClosedOpen=>Closed
    Wed Feb 24 08:58:13 2016aginorStatusConfirmed=>Fixed
    Wed Dec 30 11:30:12 2015aginorAssigned toai0867=>aginor
    Mon Apr 20 03:38:04 2015shadowmasterStatusFixed=>Confirmed
    Tue Jul 15 04:33:36 2014shadowmasterAssigned toshadowmaster=>ai0867
    Mon Jun 16 18:12:24 2014ai0867StatusNone=>Fixed
    Tue Jan 14 05:34:26 2014shadowmasterSeverity3 - Normal=>5 - Blocker
      Assigned toNone=>shadowmaster
    Sat Sep 22 15:55:01 2012peterdesAttached File-=>Added wesnoth.log, #16599
    Show feedback again

    Back to the top

    Powered by Savane 3.1-cleanup