Logs render with transparency

[tibetiroka]

At the bottom of the launcher, the logs don't appear to be fully opaque. I'm not an expert in these things, but it looks like it uses additive blending over other windows that are rendered below, while other parts of the launcher don't. This issue is difficult to notice over regular text, but is quite visible on highlighted lines.

In this example, the launcher overlaps the github page of the project. The release version is clearly visible in the red section. If you look really closely you can also see some things render over regular text as well, however the white background stays white.

OS: Ubuntu 22.04 LTS (64-bit) with Wayland and GNOME 42.2
GPU: AMD Radeon RX 570 (with the drivers provided by the standard Ubuntu installation)

[MCOfficer]

Very strange. There is nothing in the launcher that would make it a transparent or otherwise non-standard window, and i've never seen this on either linux or windows. Are you sure this isn't some oddity of your window manager?

[tibetiroka]

This issue doesn't come up with any other applications and I haven't messed with the window manager at all, so that seems unlikely. However I have now noticed that it doesn't only happen to the logs, but to every part of the launcher.

The only thing I have noticed is that in the current version the title bar seems different. Is it possible that the GTK theme is not applied correctly? The issue persists when using light and dark theme (both standard themes).

Alright, one more weird thing is that if the game is not running, only the outline/background of the buttons on the screenshot seem to be affected. Here are two pictures of the buttons when a dark and a white window is rendered below:


The text is not visible through the buttons.

For reference, the mentioned title bar:

This is not consistent with other applications.

[MCOfficer]

Hm. I don't even know how to begin fixing this. Best case some future dependency update magically makes it disappear...

[tibetiroka]

Alright, here's the next update for this issue.
If I run the launcher as a regular user (eslauncher2 in terminal) the issue is present.
If I run it as the super user (sudo eslauncher2) the issue is gone. I know that running apps with sudo is a bad idea, especially that the configuration files are created per user (so if you used it as a regular user the sudo version won't see your installs), so this isn't an actual solution.
Here comes the really interesting part. If you look at the picture in the initial report, you will see an error message: No font could be found. This message is not present if you use sudo. Also, with sudo, the title bar matches the applied theme:

For reference, these are two launcher windows overlapping each other (and this github page), one of them has elevated permissions:

Now, I'm not an expert but I know that something like this should not be happening. I mean, even if somehow my user account was screwed up, other apps would be just as broken as this one. I don't know if this is an issue specific to the rust libraries you use, I don't know how many other rust apps I have (maybe you can recommend some tests), but currently that is my best bet.

Oh btw, there is no sound output in the sudo window, but that is probably normal behaviour.

[tibetiroka]

Confirmed the issue on a fresh install of Ubuntu 22.04 and on Fedora 36 (same hardware, GNOME 42.2 and 42.3, Wayland). The only difference is that on Fedora the window title text is displayed (but the rest of the title bar is still broken), and there is no 'no font could be found' error.

I know this is out of your hands, but I'm keeping this issue updated for future use anyway. Maybe it will help determine which dependency is messed up.

[leklachu]

Funny, looking at that image rings a bell from when I tried it on Ubuntu (21.10 I think; might have been 22.04). The strange, hard-to-read text and the out-of-theme title bar.

Tried on OpenSUSE Tumbleweed.... but can't run (I'll open a separate issue).

[tibetiroka]

Based on my tests, this happens on pretty much every system with Wayland. This doesn't happen on X.Org. ES itself gets some serious screen tearing on X.Org because vsync is so messed up there, but that's an other story.