I'm sorry, I will uploads the logs again. The errors shown on the original comment are because of a switcheroo-control installation and Gnome trying to run Steam with the integrated GPU (Which I guess should work too, but that's not this issue).
I'm adding new logs and a video showing the issue
As you can see on the video, once it gets into the tray bar, I can't open the window again. I can still launch games. I need to close Steam and restart it for the window to show. I'm not sure whats the cause. Can't reproduce 100% of the time
https://github.com/user-attachments/assets/918cb49e-8acc-43b7-a39c-8a5398fcc1e4
Seems like I have the same issue. It's also not 100% reproducible for me. I trigger the issue after the following
Same issue here, also on Fedora, except if I right click and press "Launch with integrated GPU" it works. I have two monitors plugged in, one to iGPU and one to my GPU (I know how bad that sounds but I'm yet to have other bugs caused by it). Steam is only displaying on the monitor plugged into my discrete GPU, if that makes a difference.
I have the same issue, seems like it always happens after closing a game, if the steam window was minimized
OS Name: Fedora Linux 41
OS Type: 64-bit
GNOME Version: 47
Windowing System: Wayland
Kernel Version: Linux 6.12.5-200.fc41.x86_64
This is weird. Setting steam to start in Big Picture Mode prevents this bug. However, when in Browser Mode, this bug happens after I run steam for the first time, exit steam, and run it again. The issue persists and does not resolve until I start steam in Big Picture Mode again or reboot the laptop.
OS Name: Fedora Linux 41
OS Type: 64-bit
GNOME Version: 47.5
Windowing System: Wayland
Kernel Version: 6.13.12-200.fc41.x86_64
After leaving fedora 41 for a month and sitting on windows same bug appeared for me. Restarting steam didn't help, but i decided to start steam via terminal and this bug dissapeared
Same issue for me. When starting any game, the main window minimizes and can't be viewed again. Friends list stays visible. Games can still be started by right-clicking the tray-icon and will work, but a message asking if the game should be uninstalled appears.
~I was able to get around the issue by setting STEAM_USE_X11=1 and running it through XWayland.~
edit: disregard, setting the env didn't change anything.
OS Name: Arch Linux
OS Type: 64-bit
Windowing System: Wayland
DE / WM: Hyprland
Kernel Version: 6.15.1-arch1-2
Steam version:
Steam Beta Branch: Stable Client
Steam Version: 1747701111
Steam Client Build Date: Mon, May 19 9:51 PM UTC -08:00
Steam Web Build Date: Tue, May 20 2:21 AM UTC -08:00
Steam API Version: SteamClient022
@philkoch I'm confused. Steam doesn't support Wayland, and only ever runs in Xwayland. I've never seen the STEAM_USE_X11 var referenced anywhere. Are you sure this isn't just placebo?
Yes, you're right. I've checked with hyprctl clients and steam is using xwayland no matter if the env is set or not. Problem is also still occuring occasionally. It seems that not using the STEAM_USE_X11-env solved the problem for me, but that steam disappearing after playing doesn't happen every time, which lead me to believe setting the env worked.
On my case I think this is related to Steam crashing on the background, seems to happen always I get an achievements, but maybe happens with some other triggers. One this happens, the achievement notification appears twice for example.
Disabling GPU acceleration for the client I don't reproduce the issue.
For those having issues... Do you people have an integrated GPU on your systems?
For those having issues... Do you people have an integrated GPU on your systems?
No, just a discrete AMD Radeon RX 6700 XT graphics card:
Manufacturer: ASUSTeK COMPUTER INC.
Model: PRIME B350M-A
System Size: Desktop
No touch input detected
Processor Specifications:
CPU Manufacturer: AuthenticAMD
CPU Brand: AMD Ryzen 9 5900X 12-Core Processor
"Fedora Release 41 (Forty One)" (64-bit)
Kernel Name: Linux
Kernel Version: 6.15.7-100.fc41.x86_64
X Server Publisher: The X.Org Foundation
X Server Version: 12401008
X Window Manager: GNOME Shell
Steam Runtime Version: steam-runtime_1.0.20250519.130917
Driver: AMD Radeon RX 6700 XT (radeonsi, navi22, LLVM 19.1.7, DRM 3.63, 6.15.7-100.fc41.x86_64)
Driver version: 4.6 (Compatibility Profile) Mesa 25.0.7
Desktop color depth: 24 bits per pixel
Monitor refresh rate: 143 Hz
Can you check coredumpctl when this happens again to see if it's because of steamwebhelper crashing?
Hmm, I've got this from coredumpctl:
TIME PID UID GID SIG COREFILE EXE SIZE
Mon 2025-07-21 16:31:57 CEST 790460 1000 1000 SIGILL present /home/finn/.local/share/Steam/ubuntu12_64/steamwebhelper 74.2M
Mon 2025-07-21 16:33:52 CEST 795829 1000 1000 SIGILL present /home/finn/.local/share/Steam/ubuntu12_64/steamwebhelper 64.7M
Mon 2025-07-21 17:06:01 CEST 790024 1000 1000 SIGSEGV present /home/finn/.local/share/Steam/ubuntu12_32/steam 66.9M
Mon 2025-07-21 19:09:34 CEST 848572 1000 1000 SIGILL present /home/finn/.local/share/Steam/ubuntu12_64/steamwebhelper 71.8M
Mon 2025-07-21 19:39:01 CEST 848117 1000 1000 SIGSEGV present /home/finn/.local/share/Steam/ubuntu12_32/steam 34M
Tue 2025-07-22 09:46:34 CEST 874328 1000 1000 SIGILL present /home/finn/.local/share/Steam/ubuntu12_64/steamwebhelper 75.9M
Tue 2025-07-22 10:16:01 CEST 873884 1000 1000 SIGSEGV present /home/finn/.local/share/Steam/ubuntu12_32/steam 44.8M
...
Sat 2025-08-02 19:17:01 CEST 904701 500 500 SIGSEGV present /opt/media/apps/Steam/ubuntu12_32/steam 40.9M
I think this happens when the steamwebhelper crashes, because of some issue with hardware acceleration and I think it's related to https://github.com/ValveSoftware/steam-for-linux/issues/11942 too, this is a secondary effect of that crash.
I have the same issue.
Arch Linux
Kernel 6.16
Hyprland
Wayland
GPU RX 5700 XT
Mesa 1:25.1.7-1
Your system information
Please describe your issue in as much detail as possible:
Describe what you expected should happen and what did happen. Please link any large code pastes as a Github Gist
Steps for reproducing this issue:
Doesn't happen always but it's with the window closed and trying to open again while still running on the background
Logs: