Hello @rokejulianlockhart, this issue was previously evaluated, but I'm having some trouble digging up the older issue report.
From memory, Steam's self-updater process intentionally doesn't use any major frameworks to decorate the window so that there's as few points of failure as possible, and as a result, that also reduces the number of scenarios that would prevent the Steam client from being able to bootstrap itself. Reliability takes priority over cosmetics in this case.
https://github.com/ValveSoftware/steam-for-linux/issues/9745#issuecomment-1611479192
@kisak-valve, probably better to close as "not planned" then, right?
https://github.com/ValveSoftware/steam-for-linux/issues/9745#issuecomment-1611479192
@kisak-valve, this might be worth revisiting, because multiple distributions - Fedora 41+ - and desktop environments - GNOME 40+ and KDE Plasma 6+ - have switched to being Wayland-only whereas that installer runs under XWayland.
I presume we both agree that that's a rather significant point of failure - that is, running under not merely a nested compositor, but display server? Irrespective of what graphical toolkit it uses, it should be native Wayland, because XWayland isn't as stable.
When installing Steam, one of the windows ultimately renders as a Qt or GTK window.It looks great, especially on KDE Plasma (important for Steam Deck).
I've updated the original issue to demonstrate the actual inconsistency amongst the dialogs, too. It appears that the rest were recently updated from a toolkit that chose Qt or GTK3 to solely GTK4 dialogs.
https://github.com/ValveSoftware/steam-for-linux/issues/9745#issuecomment-2517650114
@kisak-valve, even more importantly, it's not DPI-aware, so it's nigh unreadable at 150% scale on a 16-inch 2560 by 1440-pixel monitor:
Should I file this separately? I shall if I've no response otherwise.
Nice way to passive aggressively demand a response.
I've already communicated the critical information here with the need to keep this phase of Steam's bootstrapper as simple as possible so that it's reliable. Wiring a framework in to do scaling is a non-starter task.
Nice way to passive aggressively demand a response.
@kisak-valve, that wasn't my intention: I stated so because some people disable notifications on closed issues, and I believed that it was different enough to warrant a separate issue.
Certainly, if that were true, why utilise what you've just criticsed me for against me? We're both adults; if I'd been immature, I'd hope that you wouldn't lower yourself to that level.
Irrespective, enough of theoreticals: I'm not going to attempt reverse psychology on a corporation, so I wouldn't be here unless my sole intention was to assist. Remember that we're merely discussing a modal window, so thanks, sincerely, for the clarification.
tModLoader/tModLoader/issues/4315 may be relevant, if SDL renders this.
Your system information
Steam client version
Additionally, the "Steam Build Date" is
+2023-06-28T02:44-08:00.Distribution
Opted into Steam client beta?
Yes.
Have you checked for system updates?
Yes.
GPU
1 × AMD Radeon RX 5700
Please describe your issue in as much detail as possible
During installation, some of the windows are evidently GTK4. This looks good on GNOME 40, and is adequate on KDE Plasma 6 with a properly configured
gtkrc. However, the most useful window – that which displays the download progress is – is not:Unknown
GTK4 ^2
Steps for reproducing this issue