Steam from Arch-Distrobox is black-screening and not loading steam UI for me on desktop PC.

Steam from the arch-distrobox is doing..... this.......
sh: line 1: xdg-user-dir: command not found
sh: line 1: xdg-user-dir: command not found
sh: line 1: xdg-user-dir: command not found
sh: line 1: xdg-user-dir: command not found
sh: line 1: xdg-user-dir: command not found
sh: line 1: xdg-user-dir: command not found
sh: line 1: xdg-user-dir: command not found
sh: line 1: xdg-user-dir: command not found
sh: line 1: xdg-user-dir: command not found
sh: line 1: xdg-user-dir: command not found
sh: line 1: xdg-user-dir: command not found
sh: line 1: xdg-user-dir: command not found
Maybe that error spam is not ideal?
- This issue started for me sometime between yesterday afternoon and 1am my time. - Running steam from the arch-distrobox-terminal works just fine. - Running it from the old desktop shortcut or from the application menu (and there's double entries for me), leads to the black screen issue (and lack of the steam UI loading)
12 Replies
termdisc
termdisc10mo ago
what are the contents of the .desktop shortcut?
Eeyore_Syndrome
Eeyore_Syndrome10mo ago
/usr/bin/distrobox-enter for Program and -n bazzite-arch -- /usr/bin/bazzite-steam-runtime %Ufor the Argument
termdisc
termdisc10mo ago
You’re running steam manually but bazzite-steam-runtime in the shortcut. Try changing that to steam
Eeyore_Syndrome
Eeyore_Syndrome10mo ago
I was running it manually from the distrobox because otherwise it's black screening issue like in the video. Can launch games but the black screening is basically micro-input stuttering in games. I tried editing it to just steam and same issue. I deleted the desktop entry and even re-exported steam from the Arch box but that does the same thing. @nickname any luck yourself?
termdisc
termdisc10mo ago
running steam manually the way you're doing it is functionally equivalent to distrobox-enter bazzite-arch -- steam
Eeyore_Syndrome
Eeyore_Syndrome10mo ago
@termdisc @nickname I believe I solved the issue. It basically boils down to a Steam-Linux issue. Not flatpak, not distrobox. I changed the steam desktop file from: PrefersNonDefaultGPU=true to PrefersNonDefaultGPU=false and now steam launches just fine. See these issues: - https://github.com/ValveSoftware/steam-for-linux/issues/10026 - https://github.com/ValveSoftware/steam-for-linux/issues/9383 - https://github.com/ValveSoftware/steam-for-linux/issues/9940 Maybe it was making my igpu from my zen4 fighting my GPU. Not sure why it didn't affect me till very recently....
GitHub
Default steam.desktop has BAD options causing it to close and ope...
Your system information Steam client version (build number or date): Jun 21 2023 21:17:38 Distribution (e.g. Ubuntu): Ubuntu 23.10 KDE Plasma Opted into Steam client beta?: No Have you checked for ...
GitHub
New steam UI does not open if run with DRI_PRIME=1 · Issue #9383 · ...
Your system information Steam client version (build number or date): 1682634349 Distribution (e.g. Ubuntu): Fedora Silverblue 38 Opted into Steam client beta?: [Yes/No] Yes Have you checked for sys...
GitHub
Remove PrefersNonDefaultGPU=true from .desktop file of Steam · Iss...
counter-part to #7089 PrefersNonDefaultGPU is broken by design, intended to mean "Use the Discrete GPU if possible" but instead generalized to mean "Use anything that we aren't u...
tryhardsoccermomswag
Thanks for this! Yup i have 2 GPUs too AMD APU + dedicated AMD GPU
Eeyore_Syndrome
Eeyore_Syndrome10mo ago
I totally didn't spend all day trying to figure out the issue with steam in general But launching from CLI worked -.-
tryhardsoccermomswag
oh yeah thats how ive been getting around it too so annoying
Eeyore_Syndrome
Eeyore_Syndrome10mo ago
And it wasn't until the last few days I'm seeing more lemmy posts etc about this issue. No wonder it wasn't affecting my old PC as it's zen 3 no igpu.