Describe the bug
Launching SteamVR through the Steam client as a normal user shows the error A key component of SteamVR isn't working (306). Nothing shows up on the headset, and trying to restart the headset (not SteamVR) then doesn't detect the headset (106) and disables mouse input, so I can't do further tests.
I've only had some luck by running SteamVR with sudo, where despite showing the errors SteamVR failed to initialize for unknown reasons (Error: Installation Corrupt (101)), the headset starts tracking and outputting video.
Interestingly, it loads me into the "home" environment, but other VR apps/games can't seem to interact with the headset - the windows load fine most of the time, but moving the headset doesn't respond in the game, and the headset itself only displays the "empty" environment.
Also, the "home" environment says I don't have any games installed, and I can't open the dashboard, there's not even a blur or the opening sound effect when I try. After pressing the dashboard button, a simple Cannot run as root user window pops up, which probably explains that issue.
To Reproduce
Open Steam
Install SteamVR and run the setcap command to finish setup manually
Start SteamVR and watch it fail
cd to the Steam library
chown root of SteamVR
Run sudo -E ./SteamVR/bin/vrstartup.sh
Launch a game, through Steam or with sudo and observe as nothing happens
Expected behavior
I should be able to use SteamVR as a regular user. Apps being able to access the headset when SteamVR is started with sudo is probably unintended, but it's the only hope I have of playing VR games at the moment.
System Information (please complete the following information):
Distribution: Void Linux with kernel 6.0
SteamVR version: Tried with linux_v1.14 and the latest beta & stable releases
Additional context
I suspect all this is just a permissions issue. Looking through my log, I found the infamous Unable to connect to pipe errno=111, but the solution of installing missing libraries that I read in other issues doesn't make sense to me, since it works fine with sudo...
Programs not being able to interact with sudo-started SteamVR probably makes sense, since user-mode processes probably shouldn't be interacting with root processes. I was only trying to run games through it because nothing works at all as a normal user, and hopefully everything else will work as it should after fixing the normal user problem.
Describe the bug
Launching SteamVR through the Steam client as a normal user shows the error
A key component of SteamVR isn't working (306). Nothing shows up on the headset, and trying to restart the headset (not SteamVR) then doesn't detect the headset(106)and disables mouse input, so I can't do further tests.I've only had some luck by running SteamVR with
sudo, where despite showing the errorsSteamVR failed to initialize for unknown reasons (Error: Installation Corrupt (101)), the headset starts tracking and outputting video.Interestingly, it loads me into the "home" environment, but other VR apps/games can't seem to interact with the headset - the windows load fine most of the time, but moving the headset doesn't respond in the game, and the headset itself only displays the "empty" environment.
Also, the "home" environment says I don't have any games installed, and I can't open the dashboard, there's not even a blur or the opening sound effect when I try. After pressing the dashboard button, a simple
Cannot run as root userwindow pops up, which probably explains that issue.To Reproduce
setcapcommand to finish setup manuallycdto the Steam librarychown rootof SteamVRsudo -E ./SteamVR/bin/vrstartup.shsudoand observe as nothing happensExpected behavior
I should be able to use SteamVR as a regular user. Apps being able to access the headset when SteamVR is started with
sudois probably unintended, but it's the only hope I have of playing VR games at the moment.System Information (please complete the following information):
linux_v1.14and the latest beta & stable releasesScreenshots
Additional context
I suspect all this is just a permissions issue. Looking through my log, I found the infamous
Unable to connect to pipe errno=111, but the solution of installing missing libraries that I read in other issues doesn't make sense to me, since it works fine withsudo...Programs not being able to interact with
sudo-started SteamVR probably makes sense, since user-mode processes probably shouldn't be interacting with root processes. I was only trying to run games through it because nothing works at all as a normal user, and hopefully everything else will work as it should after fixing the normal user problem.