[BUG] Failed to connect to Headset Display: KDEPlasma Valve Index
Describe the bug
I get the following error-message when starting SteamVR with the Valve Index:
To Reproduce Steps to reproduce the behavior:
- Start Steam from the KDE-Menu entry (important)
- Start SteamVR
- The mentioned error occurring
After tinkering a bit, I tried to fully close Steam, and launch it from the command line (Tabby). This way it managed to connect to the ValveIndex and I can play the games.
Expected behavior I expect no error message appearing and the system to work.
System Information (please complete the following information): Please use the latest Steam beta client and SteamVR beta for your bug reports!
-
Steam client version (build number or date): 1748900261
-
SteamVR version: 2.11.2 (Beta)
-
Distribution (e.g. Ubuntu): Fedora KDE 42
-
Steam runtime diagnostics: runtime_diagnostics.txt
-
Steam and SteamVR logs: steam-logs.tar.gz]
-
Minidumps: steam-minidumps.tar.gz
Screenshots
Additional context Add any other context about the problem here.
Hello @fschaupp, can you check if this is from X-KDE-RunOnDiscreteGpu=true in /usr/share/applications/steam.desktop?
Hi @kisak-valve , I set it now to false and tried to restart my pc and steam. It doesn't seem to make a difference.
What I tried was the solution from https://github.com/ValveSoftware/SteamVR-for-Linux/issues/765#issuecomment-2564748967 : Disabling the AMD-iGPU.
So, it seems like you are definately on the right track.
Hello @fschaupp, can you check if this is from
X-KDE-RunOnDiscreteGpu=truein/usr/share/applications/steam.desktop?
I noticed, I do have a steam.desktop file in my ~/.local/share/applications/ folder too.
After setting PrefersNonDefaultGPU=false it seems to work that way.
Is there a way, to help detecting it, either in the default settings, when having an internal-iGPU and dedicated amd gpu?
(or at least having it in some FAQ pages for SteamVR and the normal steam client not launching)
It's not a fix, but a workaround is to simply restart the headset in the device menu, then restart SteamVR. At least this works on my AMD GPU on Wayland. 😅
I have the same issue. To get the headset running, I usually end up replugging the barrel connector. After a bit more looking, i notice that the Index HMD seems to be recognized as a 640x480 screen until i do so, afterwards it seems to be recognized as different hardware and not show up in the Display configuration.
Running Arch with KDE Plasma on Wayland with an AMD GPU
I have a similar issue, but when I start up SteamVR the first time after I boot it generally will halt my mouse / gui for about 30-60 seconds 1-2 times (wayland kde plasma). After system is responsive (headset doesn't work) I just quit SteamVR (do not restart SteamVR) let the steamVR window go away, and relaunch steamvr from the main steam window.
I also have audio corruption (on the headset) when I start up BeatSaber - so I switch HDMI for the headset to a different HDMI selection in the audio menu, wait a moment and switch it back.
System: GPU Radeon 7800XT CPU 5950X Headset Valve Index OS Arch Linux: Rolling
Steam Beta Branch: Steam Beta Update Steam Version: 1757452101 Steam Client Build Date: Tue, Sep 9 1:31 PM UTC -08:00 Steam Web Build Date: Tue, Sep 9 1:28 PM UTC -08:00 Steam API Version: SteamClient022
I switched from the SteamVR beta branch back to main but it seems to still apply to both.
This seems like a duplicate of https://github.com/ValveSoftware/SteamVR-for-Linux/issues/636.
Try having the headset be disconnected from the GPU while booting and only plugging it in when logged into your desktop.
Well, it seems like as of now, the only way to get it to work, was:
- Waiting for the newest fixes around (currently 2.14.2)
- unplugging the second GPU in my system (I guess that might become more common in the future, as more folks tinker with AI, right?)
Nonetheless, thanks at least for your efforts! (Yes this is a handcrafted response)