Fresh install of steam fixed nothing.
SteamVR non-Beta was briefly launching until I tried something to get it to work, not sure which thing it was that caused this behavior but it may have been related to compatibility mode and/or Proton. I found a reinstall did not help me any nor did removal of the SteamVR install directory either. What helped was switching SteamVR non-Beta to Beta and letting it reinstall that way. I got a sudo prompt when I went to launch, let it install with root, and then it finished launching thereafter. Seems to launch all the time now, though SteamVR Beta hasn't solved my other problems.
Fedora 39 x86_64, SteamVR Beta 2.4.1, HTC Vive Pro w/ Eye-Tracking
I managed to get SteamVR running with this workaround (if this can help anyone).
steam-runtime-launch-options -- %command%
A menu will pop up and set the following options:
Container runtime to: None
SDL video driver to: x11
Replying to https://github.com/ValveSoftware/SteamVR-for-Linux/issues/674#issuecomment-1951483381
I stumbled on this issue report and I wanted to add that this workaround works for me also using ALVR!
Specs:
OS: Fedora 40 KDE Plasma
Kernel: 6.8.9-300.fc40
DE: Plasma 6.0.4
CPU: Intel i7-12700k
GPU: AMD Radeon RX 6900XT
SteamVR: 2.4.4
Steam/SteamVR/ALVR all flatpak versions
none of your guys' fixes worked and steamvr talks about running it in sniper slr but i dont know what that is and its also any version of steamvr too
it also says that it is unable to find the steam run time
it also seems to try and load a file of which doesnt exist in /root/steam/.steam/
Nothing extracted yet.
Describe the bug
SteamVR asks for superuser, I enter my password, and every time I attempt to run it, the launch button goes to "Stop" then "Launch" again.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
SteamVR to launch normally.
System Information (please complete the following information):
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Note: Commenters who are also experiencing this issue are encouraged to include the "System Information" section in their replies.