1.12 on Debian Stretch Crashes on Fullscreen

[evilmaus]

The game crashes for me when I try to take it full screen. It doesn't do this on other systems, though on one other computer, I completely lose all video from the system when I take Wesnoth fullscreen. It may be related. at any rate, this is the information that I've been able to get from the program on crash:

Code: Select all

(gdb) run
Starting program: /usr/games/wesnoth-1.12 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
process 11199 is executing new program: /usr/games/wesnoth-1.12
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe8457700 (LWP 11200)]
Battle for Wesnoth v1.12.5
Started on Sun May 15 11:20:52 2016


Data directory: /usr/share/games/wesnoth/1.12
User configuration directory: /home/user/.config/wesnoth
User data directory: /home/user/.local/share/wesnoth/1.12
Cache directory: /home/user/.cache/wesnoth
[New Thread 0x7fffe3642700 (LWP 11201)]
[Thread 0x7fffe3642700 (LWP 11201) exited]
[New Thread 0x7fffe3642700 (LWP 11202)]
20160515 11:20:54 warning font: Failed opening font file 'DroidSansJapanese.ttf': No such file or directory
Checking video mode: 1280x720x32...
setting mode to 1280x720x32
20160515 11:20:54 warning font: Failed opening font file 'DroidSansJapanese.ttf': No such file or directory
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  151 (XFree86-VidModeExtension)
  Minor opcode of failed request:  10 (XF86VidModeSwitchToMode)
  Value in failed request:  0x1d5
  Serial number of failed request:  225
  Current serial number in output stream:  227
[Thread 0x7fffe3642700 (LWP 11202) exited]
[Thread 0x7ffff7f2db00 (LWP 11199) exited]
[Inferior 1 (process 11199) exited with code 01]
(gdb) bt
No stack.
(gdb) catch throw
Catchpoint 1 (throw)
(gdb) run
Starting program: /usr/games/wesnoth-1.12 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
process 11281 is executing new program: /usr/games/wesnoth-1.12
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe8457700 (LWP 11282)]
Battle for Wesnoth v1.12.5
Started on Sun May 15 11:22:43 2016


Data directory: /usr/share/games/wesnoth/1.12
User configuration directory: /home/user/.config/wesnoth
User data directory: /home/user/.local/share/wesnoth/1.12
Cache directory: /home/user/.cache/wesnoth
[New Thread 0x7fffe3642700 (LWP 11283)]
[Thread 0x7fffe3642700 (LWP 11283) exited]
[New Thread 0x7fffe3642700 (LWP 11284)]
20160515 11:22:43 warning font: Failed opening font file 'DroidSansJapanese.ttf': No such file or directory
Checking video mode: 1280x720x32...
setting mode to 1280x720x32
20160515 11:22:43 warning font: Failed opening font file 'DroidSansJapanese.ttf': No such file or directory
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  151 (XFree86-VidModeExtension)
  Minor opcode of failed request:  10 (XF86VidModeSwitchToMode)
  Value in failed request:  0x1d5
  Serial number of failed request:  212
  Current serial number in output stream:  214
[Thread 0x7fffe8457700 (LWP 11282) exited]
[Thread 0x7ffff7f2db00 (LWP 11281) exited]
[Inferior 1 (process 11281) exited with code 01]

[Iris]

Although it’s not possible to rule out a bug in Wesnoth (or SDL 1.2) itself with that information, there are a couple other things you didn’t mention that may be playing a part in this:

• Your graphics hardware and drivers (in particular to verify that the mode Wesnoth is trying to use is actually supported)
• Your window manager and/or desktop environment

For the record, I am using Debian stretch as well and I don’t get this on KDE’s window manager with the NVIDIA proprietary drivers.

[evilmaus]

I'm running XFCE and using the NVIDIA proprietary drivers for one of the Maxwell generation cards. It's an HTPC with Steam, emulators, and hopefully Wesnoth on it. Hot-seat fun. I have the debug symbols installed, along with gdb, so if guided through to extracting pertinent information, I should be able to deliver on that.

[Aginor]

I'm running XFCE and using the NVIDIA proprietary drivers for one of the Maxwell generation cards. It's an HTPC with Steam, emulators, and hopefully Wesnoth on it. Hot-seat fun. I have the debug symbols installed, along with gdb, so if guided through to extracting pertinent information, I should be able to deliver on that.

From my understanding, I don't think this is directly a wesnoth problem, but rather some bad interaction between the nvidia drivers and your X-server. I don't own any nvidia hardware myself, but I suggest you search for the X-related error message from above and see if you find anything useful.

Results such as this one is what's led me to that conclusion: https://bbs.archlinux.org/viewtopic.php?id=195435