-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linux SteamVR broken slimevr: bridge error: No such file or directory #43
Comments
I haven't heard anyone else using the driver in linux having this issue 🤔 |
not sure it its new first time trying to use SlimeVR. I am currently running Arch linux with SteamVR 2.2.1 Beta. |
I just entered latest stable SteamVR with |
Latest beta also has an existing |
|
I can also |
intressting, may the vrserver is started diffrently based on the host system, not sure what valve is doing. with a custom build and the sockets moved to |
btw just curious, you are using |
no flatpak/snap in use. steam comes from the arch pkg |
this is needed if the vrserver is running in a chroot env and we need to mount the sockets to the HOME dir. see: SlimeVR/SlimeVR-OpenVR-Driver#43
btw i asked for someone with SteamVR experience to check this issue. |
sure, have not found the place where the isolation from the host system happens yet. |
Could you try to run SteamVR with Steam play none as the compatibility layer(install using protonup-qt) |
Reason being is SteamVR is running under Valve's runtime and they may have changed how it works in this beta this would confirm that's the case |
with Steam-Play-None SteamVR UI is not starting. |
Do you have all the dependencies needed to see that try installing steam-native-runtime |
tried, but same result. steps:
|
Run steam in a terminal and send the output here |
You have tried previous versions right and only 2.2.1 is affected? |
tested with Beta and Release Steam-Play-None + Betafrom looking at the logs I think this are the core problems:
|
You can tell the Steam Linux Runtime to expose SlimeVR's IPC file within its sandbox by putting Edit: if it wasn't clear, adding that launch option fixes SlimeVR |
anyway if you truely believe this to be a steamvr issue you can always report it here(the not launching part(https://github.com/ValveSoftware/SteamVR-for-Linux/) |
yes, can confirme adding I dont think that Steam-Play-None is supported by Valve , they have ther runtime for a reason, |
can you report this to https://github.com/ValveSoftware/steam-runtime/issues please, I honestly feel like |
#43) (#44) * add $HOME/.local/share/slimevr to the possible dirs of the sockets (fix #43) * Don't throw exception when socket fails to open Co-authored-by: Uriel <[email protected]> * Add path constants Co-authored-by: Kitlith <[email protected]> * Update src/bridge/bridge-unix-sockets.cpp Co-authored-by: Kitlith <[email protected]> * fixup! --------- Co-authored-by: Kitlith <[email protected]> Co-authored-by: Uriel <[email protected]>
currently using SlimeVR on Linux with SteamVR is not possible.
error message from vrserver:
after some debugging I noticed that this comes from the fact that the vrserver is started in a chroot like envirement and has no access to the host files system.
this means /tmp and /run/user/1000 are not the same as the host system sees, and as a result the sockets from the slimeVR server are not there from the point of view of vrserver or the slimevr driver.
How to easy see the chroot mounts:
cat /proc/$(pidof vrserver)/mounts
How to explore the chroot isolation:
sudo nsenter -m -t $(pidof vrserver) bash
The text was updated successfully, but these errors were encountered: