Widelands crashes in fullscreen

[wl-zocker]

Found on r7670 on Win10. It only happens in fullscreen mode, but then for every resolution I tried. I am not exactly sure how many different bugs I describe.

Singleplayer -> New Game:
When I move the mouse for the first time, the background moves a bit upwards. Every time I move the mouse, the bottom of the screen flickers. I am unable to click on OK or Cancel. See attached screenshots.
It is possible to start a map by double-clicking on it. When I click on "Start Game" in the next dialog, the screen gets white and Widelands crashes.

Multiplayer -> LAN -> New Game -> Map:
As soon as I move the mouse pointer, I get the white screen and Widelands does not respond any more.

Editor:
Even when I do not use the mouse pointer, I get a white screen and a crash.

In all three cases, the stderr.txt is empty. The last few lines from stdout.txt are unsuspicious:
Normal game/Multiplayer:
**** GRAPHICS REPORT ****
 VIDEO DRIVER windows
 pixel fmt 370546692
 size 1600 900
**** END GRAPHICS REPORT ****
[Host]: starting up. // Only in multiplayer

Editor:
**** GRAPHICS REPORT ****
 VIDEO DRIVER windows
 pixel fmt 370546692
 size 1600 900
**** END GRAPHICS REPORT ****
Loading the world took 877ms
Font file not found. Falling back to serif: serif
Could not find file: could not find file or directory: i18n/fonts/serif

(The missing font file also happens in windowed mode.)

All other menus are fine, and replays work, too.

I usually do not play in fullscreen mode, so I cannot tell when this issue appeared for the first time.

[Hans Joachim Desserud (hjd)]

Thanks for reporting.

I'm not able to trigger this in fullscreen on Ubuntu (WL r7679), but it might be a Windows-only/driver issue.

Could go a bit more into detail about how you switched to fullscreen/how to trigger this? Also, did you change the resolution at the same time?

I've had issues with Widelands in the past when changing resolution. In that case the game would expand the window to a larger size, but if you moved the cursor there it failed (or "flickered") when attempting to render these new parts. I *think* buttons were still possible to click if you managed to click the right section when moving the cursor downwards to the cancel button, but I don't remember whether they did or not.

[Albert Einstein (w-aaaaa)]

I have the same issue. But only on FIRST SCREEN.
I opened main menu, then I've pressed "f" button (fullscreen mode). Then the standard window moved to the top left and the rest of the window is filled with black. Possible issue: the fullscreen mode is switching in a wrong way. The window is not redrown correctly. It is needed to make completely new window.

[wl-zocker (wl-zocker)]

I used the options menu to switch to fullscreen and/or to change the resolution (actually, there is no need to change the resolution at all to trigger this bug). Afterwards, I'm in the main menu (which shows no glitches) and I quit Widelands normally. Now I restart it and it uses the new settings. Now, I can still see the issues described.
I also have the flickering when I go to the New Game menu directly after changing the options, without restarting Widelands.

If I use f to toggle the fullscreen mode, I get black areas, as described in #4. Everything still behaves as if I were in windowed mode. If I use f in the main menu and the go to New Game screen, it haves as described in the original report (flickering etc.). If I go back to windowed mode, the screen gets truncated (which happens to every screen). Pressing f once more leaves me with a black area only at the bottom (the area where the flickering occured).

[kaputtnik (franku)]

See also bug 1459529 where i posted another screenshot in #6: https://bugs.launchpad.net/widelands/+bug/1459529/comments/6

I am on linux.

[Albert Einstein (w-aaaaa)]

@kaputtnik: that is what I can see on Windows now :)

[TiborB (tiborb95)]

f key misbehaves on arch linux as well. But I could not get no other issues described above

[wl-zocker (wl-zocker)]

So we have the problem with the f key, which has been reported in another report (bug 1459529).

And then there are one or two bugs (flickering; white screen + crash) that only I encounter so far and that seem unrelated to the other issue because they also happen when I switch to fullscreen in the menu and restart afterwards. This might be some incompatibility from my laptop. (If noone else sees these issues, I don't mind if you set it to Invalid. I usually play in windowed mode.)

[Hans Joachim Desserud (hjd)]

Yes, I agree there's probably multiple issues here.

I had another look at bug 1459529 and experimented a bit. By holding down 'f' for a longer period of time on the main menu I believe I was able to trigger the same flickering. The right and bottom side of the window would flash each time I moved the cursor. I seemed to resolve itself when I clicked on one of the menu entries though. Haven't been able to trigger a crash yet, but it looks like the flickering is a real issue (this is on Ubuntu).

Albert: were you able to trigger a crash too, or just the f key problem?

[Launchpad Janitor (janitor)]

[Expired for widelands because there has been no activity for 60 days.]

[SirVer (sirver)]

Let's focus on the crash in this bug, the other issues seem covered in other bugs. Is that reproducible for any dev?

[GunChleoc (gunchleoc)]

I can't reproduce this on Windows 7 or Ubuntu.

[kaputtnik (franku)]

I can't reproduce the crash or malfunction mouse pointer anymore. Something like the Screenshot i have posted didn't show up here anymore.

Screenshot:
https://bugs.launchpad.net/widelands/+bug/1459529/+attachment/4541269/+files/Screenshot_20151228_121028.png

Nevertheless the menus do not take care of the fullscreen toggle. The result is that you have black borders when switching to fullscreen, or some of the buttons/menus are not reachable anymore when switching to window mode. See bugs
- bug 1398733 "Fullscreen Menus cannot relayout themselves"
- bug 1598588 "Child Windows doesn't change position when toggling to window mode" (duplicate of former one)

I believe this bug is solved when the other bugs are solved...

[SirVer (sirver)]

since the crash that is a blocker seems gone I am closing this issue as fixed.

The other two bugs are not targeted for b19 (due to extensive refactoring required), we will need to tackle them for b20 though.

[GunChleoc (gunchleoc)]

Fixed in build19-rc1.