Crashing when I switch screens

[Atreides]

Not sure this is wesnoth's fault at all but maybe someone can help out. The latest flatpak download of 1.16.10 crashes when I switch screens using CTRL F1-4 (Linux btw). I did check the linux logs first time and it had some error about SDL. Probably a bug in the graphics software of Debian Buster (yeah I'm a little behind still, working on it!). Workaround is to just run the game and not switch but I am hopeful maybe I can do something to fix it. Incidentally I can switch all I like with 1.14 (flatpak also) & 1.12 (debian installed) so it really seems to be something 1.16.10ish (1.16.2 was fine btw!).

[Pentarctagon]

What was the error?

[Atreides]

Nov 22 18:24:47 smaug kernel: [384847.168311] wesnoth[5851]: segfault at 7f0c8d50e010 ip 00007f0caf24d7b1 sp 00007ffeb4733210 error 4 in libSDL2-2.0.so.0.2400.0[7f0caf1c8000+111000]

I was just gonna add that to my post after I realized I ought to. : )

[Pentarctagon]

Just that doesn't really tell me much, unfortunately.

[gnombat]

It sounds kind of like #7438 although I thought that was Windows-only...

Does it make any difference whether you run Wesnoth in full screen or not?

[Atreides]

It sounds kind of like #7438 although I thought that was Windows-only...

Does it make any difference whether you run Wesnoth in full screen or not?

Not only is that windows but it's 1.17 I think. Although it could of course have a bug carried over from 1.16...

I always run it full screen but I could try that. Now here's the funny thing. After posting the error it, uh, stopped happening. Yes, I think my computer is out to get me. : )

I'll post more info if I can find any.

[Atreides]

Something is odd about 1.16.10...

I just got this:

Battle for Wesnoth v1.16.10 x86_64
Started on Thu Dec 7 10:52:45 2023

20231207 10:52:45 error display: Could not initialize SDL_video: No available video device
Could not initialize video.

Video initialization failed

Exiting.

Seconds later I tried 1.17

Battle for Wesnoth v1.17.23+dev (05b4db8c-Clean) x86_64
Started on Thu Dec 7 10:52:59 2023


Data directory: /app/share/wesnoth
User configuration directory: .var/app/org.wesnoth.Wesnoth/config/wesnoth117
User data directory: /home/USER/.var/app/org.wesnoth.Wesnoth/data/wesnoth/1.17
Cache directory: /home/USER/.var/app/org.wesnoth.Wesnoth/cache/wesnoth


Setting mode to 1920x1080
Checking lua scripts... ok

All fine!

What is going on?


P.S. I rebooted and it's OK now. Old DOS trick. Heh. I read that Linux is so stable and all that but seems going 80's style on it still works.

[Atreides]

Something is definitely odd with the latest 1.16's video.

Not sure this is any use but it crashed in full screen mode when I switched virtual desktops.

Log hasn't much in it but maybe it means something to somebody.

[Atreides]

Hmmm, I've tried turning off Wesnoth's full screen checkbox and set up the fullscreen in my window manager KDE/Plasma (whatever it is) and it seems to work fine now. It looks identical so there's no downside!

Speaking broadly I suspect that BfW's fullscreen toggle is not very compatible with all systems and it's wiser to use the system full screen instead.

[Wedge009]

I don't check forums often so sorry for the late reply. But I just wonder if the issues you're having may be from possible hardware and/or driver issues? I find Wesnoth's toggling between windowed and full-screen mode very smooth on Plasma. That's for both Wesnoth 1.16 and 1.18.

The issues with windowing I've seen reported on GitHub seem to be on less-commonly used desktop environments.