As a maintainer of WiVRn, I've had a few reports of users trying to use Vivecraft from Prism launcher through flatpak.
Vivecraft uses OpenVR, which stores its configuration in xdg-config/openvr.
We implement OpenVR on top of OpenXR, so it also requires access to xdg-config/openxr.
Both OpenVR and OpenXR work by dynamically loading shared libraries, depending on the installation method, those will be in one of the following paths: /var/lib/flatpak/app/io.github.wivrn.wivrn, xdg-data/flatpak/app/io.github.wivrn.wivrn or /usr/lib/. Because of flatpak design, paths under /usr will not work.
Finally, runtime communication between the shared library and the server process is done through xdg-run/wivrn
It would be possible to support WiVRn by default by adding the following permissions:
--filesystem=xdg-run/wivrn:ro
--filesystem=xdg-data/flatpak/app/io.github.wivrn.wivrn:ro
--filesystem=/var/lib/flatpak/app/io.github.wivrn.wivrn:ro
--filesystem=xdg-config/openxr:ro
--filesystem=xdg-config/openvr:ro
This will not work for Monado: it uses xdg-run directly for IPC, and stores its files in /usr as there is no flatpak distribution.
As a maintainer of WiVRn, I've had a few reports of users trying to use Vivecraft from Prism launcher through flatpak.
Vivecraft uses OpenVR, which stores its configuration in
xdg-config/openvr.We implement OpenVR on top of OpenXR, so it also requires access to
xdg-config/openxr.Both OpenVR and OpenXR work by dynamically loading shared libraries, depending on the installation method, those will be in one of the following paths:
/var/lib/flatpak/app/io.github.wivrn.wivrn,xdg-data/flatpak/app/io.github.wivrn.wivrnor/usr/lib/. Because of flatpak design, paths under/usrwill not work.Finally, runtime communication between the shared library and the server process is done through
xdg-run/wivrnIt would be possible to support WiVRn by default by adding the following permissions:
This will not work for Monado: it uses
xdg-rundirectly for IPC, and stores its files in/usras there is no flatpak distribution.