Horrible graphic bug

[MikiTheBerserkr]

Today I just played my first multiplayer game. I minimized game for a few minutes. When I maximized it, it was just a black screen, and there was nothing except for a short line of pixels with alternating colors. I think those colors were red, green, and blue. The line was like 9-12 pixels long I think, and it was in the top left corner.
After a while of trying to do something about it, I heard a clock ticking, I guess this was an indicator that my turn is almost over, so seems like it was only a graphic bug.

Why does it happen!?!??! Is there no way to fix it!?!?! No way to go back into match after restarting the game?!?!?!?
Terrible first impression, terrible bug....... !!!

PS also I am on linux

[Pentarctagon]

Please provide the relevant information listed in viewtopic.php?t=25660

[MikiTheBerserkr]

I am not sure how to reproduce it, but I tried playing some more, and it happened two times more. It seems to randomly happen when playing multiplayer, and having game minimized.




The Battle for Wesnoth version 1.16.9 x86_64
Running on Ubuntu 20.04.6 LTS x86_64
Distribution channel: Steam

Game paths
==========

Data dir: /home/USER/.local/share/Steam/steamapps/common/wesnoth
User config dir: /home/USER/.config/wesnoth
User data dir: /home/USER/.local/share/wesnoth/1.16
Saves dir: /home/USER/.local/share/wesnoth/1.16/saves
Add-ons dir: /home/USER/.local/share/wesnoth/1.16/data/add-ons
Cache dir: /home/USER/.cache/wesnoth

Libraries
=========

Boost: 1.66
Lua: 5.4.2
OpenSSL/libcrypto: 1.1.1l (runtime 1.1.1f)
Cairo: 1.10.2 (runtime 1.16.0)
Pango: 1.30.0 (runtime 1.44.7)
SDL: 2.0.20 (runtime 2.26.5)
SDL_image: 2.0.5 (runtime 2.6.0)
SDL_mixer: 2.0.4 (runtime 2.6.1)

Features
========

Lua console completion: yes
D-Bus notifications back end: yes

Current video settings
======================

SDL video drivers: [x11] offscreen dummy evdev
Window size: 1366x768
Screen refresh rate: 60
Screen dots per inch: 100.861626x101.073570
Screen dpi scale factor: 1.050642x1.052850

Current audio settings
======================

SDL audio drivers: [pulseaudio] alsa pipewire dsp
Number of channels: 2
Output rate: 44100 Hz
Sample format: signed 16 bit little-endian
Sample size: 1024 bytes

Installed add-ons
=================

No add-ons installed.

[MikiTheBerserkr]

Yeah, it's caused by minimizing the game.

[MikiTheBerserkr]

when fix?

[Pentarctagon]

If it still happens for 1.16, then probably it won't be fixed at this point. Can you check if it happens on 1.17 still?

[MikiTheBerserkr]

If it still happens for 1.16, then probably it won't be fixed at this point.

If you don't care about bugs anymore, why is there still technical support forum??

Can you check if it happens on 1.17 still?

It just happened, however this time it wasn't some RGB pixels in the corner, but some weird mosaic over the whole screen.

But wait wdym 1.17 I am playing on steam and I don't have problems with multiplayer, but it says my version is 1.16.11 0.o

[Pentarctagon]

Sometimes bugs only end up getting fixed in the development version, and for one reason or another don't get backported.

1.17 is the current development version, which you can select from the BETAS tab of the game in your Steam library.

[shevegen]

I think I had a similar bug in the past. Not sure how I resolved it, but I think it may often also depend on other software you may be using, e. g. mesa, xorg-server version and what not. Some of the software you use is quite old now, such as your cairo release. Also you seem to have multiple versions installed?

OpenSSL/libcrypto: 1.1.1l (runtime 1.1.1f)
Cairo: 1.10.2 (runtime 1.16.0)
Pango: 1.30.0 (runtime 1.44.7)
SDL: 2.0.20 (runtime 2.26.5)
SDL_image: 2.0.5 (runtime 2.6.0)
SDL_mixer: 2.0.4 (runtime 2.6.1)

I just checked on these via a ruby script:

raction url1 openssl
raction url1 cairo
raction url1 pango
raction url1 sdl2
raction url1 sdl2image
raction url1 sdl2mixer

Results I got were:

https://ftp.openssl.org/source/openssl-3.2.0.tar.gz
https://www.cairographics.org/releases/ ... 8.0.tar.xz
https://download.gnome.org/sources/pang ... .14.tar.xz
https://github.com/libsdl-org/SDL/relea ... 8.5.tar.gz
https://www.libsdl.org/projects/SDL_ima ... 6.3.tar.gz
https://github.com/libsdl-org/SDL_mixer ... 6.3.tar.gz

(Edit: Seems as if the webforum here truncates too long URLs, so just the short names:
openssl-3.2.0, cairo-1.18.0, pango-1.50.14, SDL2-2.28.5, SDL2_image-2.6.3,
SDL2_mixer-2.6.3)

I maintain these URLs mostly manually, though, so there is no guarantee these are 100% the latest
stable releases - but, mostly these should be somewhat correct. So some of the software you use is
quite old.

I always try to use the latest stable releases (I compile from source) and not have more
than one version installed. This may or may not have anything to do with your issue, but
I found that this strategy works very well for me (except for boost; haven't tried the latest
stable of wesnoth yet, but often the latest boost release does not work for wesnoth, not
sure what can be done about this. C++ kind of is like a perpetually growing beast in
itself, I remember Linus' rant about boost in the past.)

I'd first try to upgrade all of that stack to the latest stable, and have it consistent too, then
see whether you can reproduce the bug, then report it on github with as much information
as possible. I would not know how to fix a bug I can not reproduce, so that would be a
dead end.