-
Notifications
You must be signed in to change notification settings - Fork 131
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
Unable to launch using Flatpak version of Steam #582
Comments
Going to close out hopefully issue resolved if not please re-open. |
@ykeara nothing has changed, flatpak'ed steam still don't support launching appimages. |
@ykeara This is not resolved unfortunately. Single-binary AppImages cannot be run in nested containerisation situtaions like Flatpak, Snap, NixOS' FHSEnv or even the Steam Linux runtime. Is there a specific reason why OVRAS is distributed as a single AppImage file rather than in its extracted form on Steam? In NixOS, we have an appimage-run wrapper which unpacks the AppImage and then runs the extracted binary because we can't run AppImages directly. Prepending that in the run.sh script makes OVRAS work just fine. |
There is a fix for anyone who still wants to get this to work. Don't use proton, and go to the files, and edit run.sh to this:
|
Trying to run on NixOS, and hitting this issue. I tried to set run.sh to the following:
And it gets farther, but then I get:
I suggest this issue should be reopened. |
Describe the bug
A Flatpak distribution of Steam exists as a simplified method of distributing Steam. The AppImage runtime requires
libfuse
to run, but the distribution does not include it.To Reproduce
Steps to reproduce the behavior:
Expected behavior
OVR Advanced Settings to launch.
Screenshots
Console output log when attempting to launch the app:
Software (please complete the following information):
Hardware (please complete the following information):
Additional context
This is a known issue with Flatpak attempting running AppImage as setuid root is not available inside the sandbox. RetroArch has moved away from using AppImage to the Steam Soldier runtime, and the suggestion has been raised to SuperTuxCart to do the same. A recent upstream issue flathub/com.valvesoftware.Steam#770 might contain some useful information if this is something worth solving.
The text was updated successfully, but these errors were encountered: