Skip to content
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

Check flatpak runtime dir first on Linux #48

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

0chroma
Copy link

@0chroma 0chroma commented Sep 18, 2024

This change would allow SlimeVR to work when the server is running inside a flatpak.

This change has SlimeVR look for sockets in $XDG_RUNTIME_DIR/app/dev.slimevr.SlimeVR before other locations, since this is the only place inside $XDG_RUNTIME_DIR SlimeVR-Server can write to when running inside a flatpak.

If Steam is also running inside a flatpak, we can gain access to this folder on the host by running flatpak override --user --filesystem=xdg-run/app/dev.slimevr.SlimeVR:create com.valvesoftware.Steam.

@ImUrX
Copy link
Member

ImUrX commented Sep 19, 2024

SteamVR beta has sandboxed $XDG_RUNTIME_DIR, I don't think we should keep using it

@0chroma
Copy link
Author

0chroma commented Sep 19, 2024

I see. If you'd like, I can modify it to look in ~/.var/app/$FLATPAK_ID instead.

That's too bad since the runtime dir is technically where it belongs

@ImUrX
Copy link
Member

ImUrX commented Sep 19, 2024

i guess the current idea is to go to XDG_DATA_DIRS instead

@ImUrX
Copy link
Member

ImUrX commented Oct 30, 2024

I see. If you'd like, I can modify it to look in ~/.var/app/$FLATPAK_ID instead.

That's too bad since the runtime dir is technically where it belongs

but you just set your launch argument to this and it magically fixes steamvr:
~/.local/share/Steam/steamapps/common/SteamVR/bin/vrmonitor.sh %command%

it can see $XDG_RUNTIME_DIR if you do this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants