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 22 Sep 2012 03:55:01 PM UTC  
 
Category: BugSeverity: 5 - Blocker
Priority: 5 - NormalItem Group: User Interface
Status: NonePrivacy: Public
Assigned to: Ignacio R. Morelle <shadowmaster>Open/Closed: Open
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.

 

Mon 20 Jan 2014 03:51:14 AM UTC, 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 22 Sep 2012 03:55:01 PM UTC, 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):
   
   
Comment:
   

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 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.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 3 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Tue 14 Jan 2014 05:34:26 AM UTCshadowmasterSeverity3 - Normal=>5 - Blocker
      Assigned toNone=>shadowmaster
    Sat 22 Sep 2012 03:55:01 PM UTCpeterdesAttached File-=>Added wesnoth.log, #16599
    Show feedback again

    Back to the top


    Powered by Savane 3.1-cleanup