protonscr

Steam GUI Broken Into Separate Xorg Windows Until Restarted

steamclosed Steam client
ValveSoftware/steam-for-linux#9786 · opened 2023-07-03 by MkThUnderwd · updated 2024-09-24 · 28 comments · github
MMkThUnderwd 2023-07-03 github

Your system information

  • Steam client version (build number or date):
    Steam Version: 1687386907
    Steam Client Build Date: Wed, Jun 21 16:18 UTC -06:00
    Steam Web Build Date: Wed, Jun 21 17:26 UTC -06:00
    Steam API Version: SteamClient020

  • Distribution (e.g. Ubuntu): - Xubuntu 22.04.2 LTS x86_64

  • Opted into Steam client beta?: [Yes/No] - NO

  • Have you checked for system updates?: [Yes/No] - YES

These packages were not updated at the time:

libmm-glib0
linux-firmware
modemmanager
php8.1-cli
php8.1-common
php8.1-opcache
php8.1-readline
php8.1-xml
python3-renderpm
python3-reportlab
python3-reportlab-accel
ubuntu-drivers-common

  • Steam Logs: [generate by running this command in a terminal tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]
    2023-07-02_mkthunderwd_steam-logs.tar.gz
  • GPU: Nvidia/Intel/AMD - AMD Radeon RX 6700 XT (navi22, LLVM 15.0.7, DRM 3.51, 5.15.0-75-generic) (0x73df)

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

This screenshot says it all. All the popup windows of Steam were broken out into their own generic-icon Xorg windows:
STEAM_GLITCH_Screenshot_2023-07-03_18-05-39_1

Steps for reproducing this issue:

  1. I have not idea how to make it occur. It happened while I was away from my computer.

I hope this helps figure out a cause. This is the first time I've seen this kind of error that I can remember.
See Steam request thread here:
HelpRequest HT-986N-WC65-3Q22

CCaffeineix 2023-07-05 github

This happened to me after waking from suspend, so that might have something to do with it. It looks like the exact same issue, black window and UI in top-left corner.

Jjasuka 2023-07-05 github

This also happens to me when the PC is idling for a longer period of time (for example overnight) with locked screen.

Nnijave 2023-07-07 github

Same over here on Fedora 37. They only show up after sitting idle overnight so far. Other logs and screenshot attached to #9806

Edit: I'm also using a KVM to switch to my work machine which effectively disconnects both displays--I see some errors related to that in the logs

Edit2: Not sure if related, but I tried to close the windows and steamwebhelper crashed then it brought down Cinnamon with it

$ coredumpctl list steamwebhelper
TIME                            PID  UID  GID SIG     COREFILE EXE                                                       SIZE
Tue 2023-06-20 16:47:33 EDT  455405 1000 1000 SIGSEGV missing  /home/nick/.local/share/Steam/ubuntu12_64/steamwebhelper   n/a
Thu 2023-07-06 16:27:35 EDT    7359 1000 1000 SIGSEGV present  /home/nick/.local/share/Steam/ubuntu12_64/steamwebhelper 56.3M
Thu 2023-07-06 19:01:36 EDT 1199810 1000 1000 SIGILL  present  /home/nick/.local/share/Steam/ubuntu12_64/steamwebhelper  8.6M
Fri 2023-07-07 16:40:36 EDT 1228342 1000 1000 SIGSEGV present  /home/nick/.local/share/Steam/ubuntu12_64/steamwebhelper 31.8M
Fri 2023-07-07 17:05:52 EDT 1515924 1000 1000 SIGSEGV present  /home/nick/.local/share/Steam/ubuntu12_64/steamwebhelper 23.1M
Bbhechinger 2023-07-11 github

This also happens to me if I leave steam running overnight.

Ddragynbane222 2023-07-16 github

I have had this happen as well, though it doesn't seem to happen on KDE, just Gnome and GTK-based desktops. hopefully that helps.

Bbhechinger 2023-07-16 github

Unfortunately I'm on KDE so we've got all bases covered I guess. :-D

Kkisak-valve maintainer 2023-07-24 github

All menu windows become visible if steam started with no monitor

Issue transferred from https://github.com/ValveSoftware/steam-for-linux/issues/9902.
@tutacat posted on 2023-07-24T11:49:53:

Your system information

  • Steam client version (build number or date): client 1689034492 (web 1689043680)
  • Distribution (e.g. Ubuntu): Fedora (XWayland)
  • Opted into Steam client beta?: No
  • Have you checked for system updates?: Yes
  • Steam Logs:
  • GPU: AMD
    steam-logs.tar.gz

Please describe your issue in as much detail as possible:

image

  • Each menu window (which should be invisible and borderless) becomes visible and bordered, due to an error when starting steam without a monitor connected.

Steps for reproducing this issue:

  1. Turn off or disconnect your monitor
  2. Open Steam
  3. Reconnect your monitor
  4. See all the menu windows visible with a border, instead of hidden
CCptCookies12 2023-08-08 github

I can confirm this also still happening to me on Steam version 1690583737 on a system running Fedora 38 with KDE Plasma and Wayland, and using an AMD Radeon 6700 XT. It only happens if I turn off my two monitors with Steam running overnight and usually makes me have to kill Steam in the System Monitor because it doesn't respond.

Ttutacat 2023-08-15 github

@CptCookies12 The menu windows still work. It will exit the the Exit Steam menu button, or from the taskbar icon.

MMkThUnderwd 2023-09-04 github

I'm not sure it's related but have a feeling it is.

While my (1) displayport monitor is powered off and I (2) try connecting to the same Linux machine via Steamlink app on my Android phone, Steam crashes.

steam.sh: line 798: 2187492 Segmentation fault (core dumped) "$STEAMROOT/$STEAMEXEPATH" "$@" crash_20230903195904_74.dmp[2194280]: Finished uploading minidump (out-of-process): success = yes crash_20230903195904_74.dmp[2194280]: response: CrashID=bp-83b701de-5cdc-4f3d-a081-2ecfb2230903 crash_20230903195904_74.dmp[2194280]: file ''/tmp/dumps/crash_20230903195904_74.dmp'', upload yes: ''CrashID=bp-83b701de-5cdc-4f3d-a081-2ecfb2230903''
crash_20230903195904_74.dmp.zip

Steam Version: 1690583737
Steam Client Build Date: Fri, Jul 28 13:44 UTC -06:00
Steam Web Build Date: Fri, Jul 28 17:21 UTC -06:00
Steam API Version: SteamClient020
2023-09-04_SteamDiagnostics.log
Xubuntu 22.04.3 LTS
5.15.0-82-generic

FFoxmanx7 2023-09-07 github

I am also having exactly the same issue. With the steam installed through flatpak I don´t have this issue but with the package installed from pacman I do.

Ccaphene 2023-09-21 github

Oddly, I haven't had this happen in a few days. Anyone else experiencing that as well? Nothing's really changed on my end except for maybe a few updates.

Bbhechinger 2023-09-21 github

Oddly, I haven't had this happen in a few days. Anyone else experiencing that as well? Nothing's really changed on my end except for maybe a few updates.

I've not had this issue or the VRAM leak issue since the latest update. I think they fixed it.

CCookies77777 2023-10-05 github

Oddly, I haven't had this happen in a few days. Anyone else experiencing that as well? Nothing's really changed on my end except for maybe a few updates.

Same here, around 13 days uptime and no issues anymore so I think it's fixed.

MMkThUnderwd 2023-10-11 github

I have not noticed it happening lately and I just tried it again: started Steam, turned off montior, waited a few seconds, turned monitor back on, no glitch.

Steam Version: 1696019606
Steam Client Build Date: Fri, Sep 29 12:38 UTC -06:00
Steam Web Build Date: Fri, Sep 29 15:25 UTC -06:00
Steam API Version: SteamClient020

Kkisak-valve maintainer 2023-11-24 github

Closing per the last couple comments.

SSn0uu 2024-03-08 github

I'm having this issue on Windows, has been happening the last few days. Commenting here so it isn't closed as duplicate.

Kkisak-valve maintainer 2024-03-08 github

Hello @Sn0uu, please use Steam Support to report issues you're seeing with the Steam client for Windows.

Jjoshdee 2024-03-25 github

I'm having this issue on Windows, has been happening the last few days. Commenting here so it isn't closed as duplicate.

Same here! It's getting real annoying.

DDHager 2024-03-25 github

Just chiming in that I observed this (for the first time) just now on Windows 10, so it's still happening on some platforms.

In case it offers a clue:

  1. Computer unattended to install new game (Talos Principle 2)
  2. Switched to another local Windows user account
  3. Possible sleep/resume
  4. Continued on that other account, then switched back
  5. Saw ~10 of those black windows with partial menu dropdowns
Ddragynbane222 2024-03-25 github

To all the Windows users commenting on a bug you're encountering:

  1. This is not the place for you to report that, a Valve employee has Said to go to customer support for your bugs.
  2. This is a completely unrelated bug for an operating system you do not use (Linux) that works completely differently. Any similarities are only skin deep
  3. You have not found a regression, see point 2.
  4. This project that you're reporting a bug on is specifically for Linux, as such any input you put here is useless to Valve.
AArastais 2024-04-09 github

May not be 100% related, but this exact bug/issue with the same symptoms happens if the SDL_VIDEO_DRIVER (used by SDL3) environment variable is set to wayland. In this case, it doesn't even require the steam client to be left to idle for a while; It happens as soon as steam starts. Removing the environment variable or setting it to x11 instantly fixes the issue.

Another quirk of this bug is that the mouse is misaligned on the main steam window (i.e., it's not clicking where my mouse actually is; there's an offset). I assume this is because the main window now has my system GNOME title bar attached to it.

Also, some parts of the UI are just completely broken. For example, I can't click on some games under my list of games on the left in my library screen.

Tried opting into steam client beta - didn't fix/change anything.

Distro: Arch Linux (kernel 6.8.4-arch1-1)
DE: GNOME 46.0
GPU: NVIDIA RTX 4070 (nvidia-open 550.67-5)
Protocol: wayland 1.22.0 (xorg-xwayland 23.2.5-1) [tried xorg-xwayland 23.2.6 to no avail]

Steam Beta Branch: Steam Beta Update
Steam Version: 1711734008
Steam Client Build Date: Fri, Mar 29 11:09 AM UTC -08:00
Steam Web Build Date: Fri, Mar 29 10:33 AM UTC -08:00
Steam API Version: SteamClient021

(again, tried this on non-beta and I had the same issue).

[Edit: figured out the cause of this issue and changed my comment to reflect such]

Eeranekao 2024-05-10 github

This happens to me and I'm on Windows. I know this is for Steam Linux but it's the only thread I could find about the issue, so I'm hoping that help narrowing down the causes.

Steam Version: 1709846872

It happens when I lock my Windows session or when I log into another local Windows user on my PC for a while and then re-open the Windows user session I didn't log out of.

DDavidPyke 2024-06-14 github

I have this issue too. Running Wayland on Kubuntu with a KVM switch. When I switch to the other system for more than a couple hours, I get 12 windows, one for each menu.

AASCI-Blue 2024-08-18 github

Wife has the same issue Garuda linux, dual monitor setup, Wayland, no auto logout. I also run Garuda, no problem, single monitor, power settings to always on and no auto logout.

DDeviceLimit 2024-08-23 github

I have been having this issue for a while now. On EndeavorOS KDE/Plasma 6 Wayland (and previously with KDE Plasma 5 X11) with an AMD RX6700XT graphics card.
I use a KVM to switch between this computer and another though Ive had it happen even when I didn't switch and just let the screen look and monitors standby by themselves.
I've also seen it in as little as a few hours all the way to not happening for a few days.

XXOmniverse 2024-08-26 github

Same issue, very similar setup to DeviceLimit (NVidia 4090 GPU, but exact same OS/desktop environment). Problem began after I started using Wayland.

Ccaphene 2024-09-24 github

Oddly it stopped for a bit for me, but then came back. Still the same system as previously posted in #9934

Launch options

Upstream links