Steam shows as SDL Application
Your system information
- Steam client version (build number or date): 1722380543
- Distribution (e.g. Ubuntu): Arch Linux
- Opted into Steam client beta?: Yes
- Have you checked for system updates?: YEs
- Steam Logs: steam-logs.tar.gz
- GPU: AMD
Please describe your issue in as much detail as possible:
I think that with today's beta update (But not sure at all) the client window is showing up as SDL Application instead of just Steam
Steps for reproducing this issue:
- Run regular Steam (steam-runtime on Arch) on a Gnome Wayland session
The x11 window class is changed with today update. From "steam" to "SDL Application"
"window_properties": {
"class": "SDL Application",
"instance": "steamwebhelper",
"title": "Steam",
"transient_for": null,
"window_type": "normal"
}
Assing the StartupWMClass=SDL Application to the .desktop file is a workaround for now, but would like to know if this is a bug or something expected
July 30th steam beta did this
The problem is not exclusive to Arch since I have it on Pop!_OS as well, which is a derivative of Ubuntu and falls within the Debian family of Linux distributions.
This also happens to me on Ubuntu 22.04.4 LTS
Also on Fedora 40
It happens on EndeavourOS too.
@alosarjos It works with your workaround :clap:
Also on NixOS
Just want to note I am also seeing this on Tumbleweed Linux with Gnome Wayland after the July 30th beta update.
Also present on Ubuntu 24.04 LTS. Also seems to make the client way more unstable for some reason, seeing a lot more hang-ups
Judging by what I can see, I think the change is also the reason why Steam now shows up separately from my pinned taskbar icon on KDE:
Using Xorg, but I presume it'd do the same on Wayland.
Fixed with Aug 13 update
Can confirm it's fixed here too. The patch notes didn't mention it, though.
Same here, restarting Steam and letting it apply the patch fixed the issue.
Seems also more stable currently for now compared to when the SDL version showed up. Any out-of-focus hang-ups which increased with SDL for now don't seem to occur (anymore?), but that bit would require some further testing if that was SDL-related or something deeper within the client.
Fixed