protonscr

[BUG] Failed to connect to headset display on Valve Index

steamvrclosed bug
ValveSoftware/SteamVR-for-Linux#759 · opened 2024-12-08 by StormKingVR · updated 2025-01-11 · 5 comments · github
SStormKingVR 2024-12-08 github

When I open SteamVR on KDE Plasma Wayland it tells me that the headset display failed to connect but it connects my headset, controllers, and base stations but the front headset lights stay blue and the display stays off

Steps to reproduce the behavior:
1: Install SteamVR
2: Run SteamVR with Valve Index plugged in and ready
3: SteamVR shows: Failed to connect to headset display

Expected behavior
SteamVR should open and my displays should work and i should be able to play games like i would on windows

System Information:
OS: CachyOS Linux x86_64
Kernel: Linux 6.12.3-1-cachyos
Shell: fish 3.7.1
Display (Acer KG270): 1920x1080 @ 75 Hz in 27" [Ext*
Display (ZOWIE XL LCD): 1920x1080 @ 60 Hz in 24" [E]
DE: KDE Plasma 6.2.4
WM: KWin (Wayland)
WM Theme: Breeze
Theme: Breeze (Dark) [Qt], Breeze-Dark [
Icons: breeze-dark [Qt], breeze-dark [GTK2/3/4]
Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2]
Terminal: konsole 24.8.3
CPU: AMD Ryzen 7 3700X (16) @ 4.43 GHz
GPU: NVIDIA GeForce RTX 3060 Ti Lite Hash Rate [Dis]
Memory: 7.80 GiB / 31.23 GiB (25%)
Swap: 1.18 GiB / 31.23 GiB (4%)
Disk (/): 325.60 GiB / 915.53 GiB (36%) - ext4

image

PpoVoq 2025-01-02 github

Same here with a Vive Pro on Fedora 41 KDE (wayland), on a Radeon 7600 using the SteamVR beta (Edit: also happens with the stable release). This setup used to work before, so it must be a regression either in SteamVR or KDE.

DDuckbuster 2025-01-11 github

Same here, but on Nobara OS.
I managed to get it working "once" By restarting headset and restarting SteamVR a bunch. But since then I never got video through my headset anymore.

DDuckbuster 2025-01-11 github

Why was this closed? Did you managed to fix it?

SStormKingVR 2025-01-11 github

Why was this closed? Did you managed to fix it?

I managed to fix it a while ago and forgot to close the issue, it was a faulty display port on my computer so I didn't think to close the issue since it was a hardware issue

DDuckbuster 2025-01-11 github

Ah, hardware issue, interesting. Maybe I'll try different DP port.

Nothing extracted yet.