https://github.com/ValveSoftware/steam-for-linux/issues/10933#event-12963505145
@kisak-valve, do note that it applies to both the sandboxed .flatpak and unsandboxed .RPM, if that wasn't evident. Thanks for the triage.
https://github.com/ValveSoftware/steam-for-linux/issues/10933#issue-2321965169
The reason for closing this is identical to https://github.com/ValveSoftware/steam-for-linux/issues/10464#issuecomment-2254579394 - it's apparently been remediated.
https://github.com/ValveSoftware/steam-for-linux/issues/10933#issuecomment-2254580895
This continues, but is tracked at bugzilla.rpmfusion.org/show_bug.cgi?id=6713 instead. I'll reopen if it recurs with the Flatpak. I may have erroneously closed this because I tested Steam before I had RPMFusion's FreeWorld Mesa drivers installed.
Your system information
Steam client version
download.opensuse.org/repositories/openSUSE:/Factory:/NonFree/standard/x86_64/steam-1.0.0.78-2.4.x86_64.rpmkoji.rpmfusion.org/koji/rpminfo?rpmID=939108Distributions
download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-NET-x86_64-Snapshot20240131-Media.isodownload.fedoraproject.org/pub/fedora/linux/releases/40/Spins/x86_64/iso/Fedora-KDE-Live-x86_64-40-1.14.isoOpted into Steam client beta?
Yes. Specifically, the Families' Beta.
Have you checked for system updates?
Yes
GPU
kinfostates:[^1]
[^1]:
amazon.co.uk/XFX-Radeon-5700-Boost-Ultra/dp/B07XVMXBQWPlease describe your issue in as much detail as possible
https://github.com/flathub/com.valvesoftware.Steam/assets/42837531/7ae01553-bd85-41e7-a390-bfb813bf64d6
It's somewhat self-explanatory - the GUI doesn't open most of the time. However, interestingly, a comment downstream (https://github.com/flathub/com.valvesoftware.Steam/issues/1306#issuecomment-2128387312:~:text=What i figured out is%2C when that happens%2C you can click on the tray icon and select big picture mode (which mostly would work%2C but there are times even that would not do anything)....and then exit out of big picture mode and it should take you to the normal window) has ascertained a workaround:
Steps for reproducing this issue
Log in after installation. It doesn't appear to occur until the account has been authenticated. After that, it occurs frequently, but inconsistently.