VR/ru: Difference between revisions

Line 78:

For further information about available environment variables and tweaks, read the [https://lvra.gitlab.io/docs/fossvr/monado/ Linux VR Adventures wiki] and the [https://monado.freedesktop.org/getting-started.html#environment-variables Monado documentation about environment variables]

</div>

Line 92:

Line 91:

</div>

<~~div~~ lang="en" dir="ltr" class="mw-content-ltr">

{{Warning|<span lang="en" dir="ltr" class="mw-content-ltr">Older versions of Proton will always query the current OpenVR and OpenXR runtime. If you use OpenComposite, and it fails to initialize an OpenXR context, Proton will fail to launch. A workaround is to delete the ~/.config/openvr/openvrpaths.vrpath file and then retry launching the game.</span>}}

~~{{Warning|~~Older versions of Proton will always query the current OpenVR and OpenXR runtime. If you use OpenComposite, and it fails to initialize an OpenXR context, Proton will fail to launch. A workaround is to delete the ~/.config/openvr/openvrpaths.vrpath file and then retry launching the game.}}

</~~div~~>

Line 143:

Line 140:

</div>

<~~div~~ lang="en" dir="ltr" class="mw-content-ltr">

{{Warning|<span lang="en" dir="ltr" class="mw-content-ltr">As of WiVRn version 0.23, WiVRn now manages the opencomposite paths itself. Only use the above opencomposite configuration when using versions below v0.23.</span>}}

~~{{Warning|~~As of WiVRn version 0.23, WiVRn now manages the opencomposite paths itself. Only use the above opencomposite configuration when using versions below v0.23.}}

</~~div~~>

{{File|/etc/nixos/configuration.nix|nix|3=services.wivrn = {

Line 215:

Line 210:

</div>

<~~div~~ lang="en" dir="ltr" class="mw-content-ltr">

{{Note|<span lang="en" dir="ltr" class="mw-content-ltr">Steam is run in a bubblewrap-based FHS environment. This environment runs Steam in a user namespace, which prevents it from using any capabilities or setuid binaries. This means that asynchronous reprojection can not be used on NixOS, without patching the kernel to remove these restrictions completely, or modifying the bubblewrap binary used for running Steam to remove these capability protections. Both of these workarounds come with their own security tradeoffs. See this [https://github.com/NixOS/nixpkgs/issues/217119 Nixpkgs issue]</span>}}

~~{{Note|~~Steam is run in a bubblewrap-based FHS environment. This environment runs Steam in a user namespace, which prevents it from using any capabilities or setuid binaries. This means that asynchronous reprojection can not be used on NixOS, without patching the kernel to remove these restrictions completely. See this [https://github.com/NixOS/nixpkgs/issues/217119 Nixpkgs issue]}}

</~~div~~>

Line 227:

Line 220:

</div>

<~~div~~ lang="en" dir="ltr" class="mw-content-ltr">

{{Warning|<span lang="en" dir="ltr" class="mw-content-ltr">This removes intentional restrictions from the kernel, and it could cause scheduling issues. While it has not been reported that it does cause issues, this should be considered an unsupported configuration.</span>}}

~~{{Warning|~~This removes intentional restrictions from the kernel, and it could cause scheduling issues. While it has not been reported that it does cause issues, this should be considered an unsupported configuration.}}

</~~div~~>

Line 253:

Line 244:

It is also possible to just patch amdgpu and build it as an out-of-tree module, as described in [[Linux_kernel#Patching_a_single_In-tree_kernel_module]]

</div>

=== Patching bubblewrap to allow capabilities ===

</div>

By modifying the bubblewrap binary used for running Steam, you can allow processes in that FHS environment to acquire capabilities. This removes the need for patching the kernel directly.

</div>

{{Warning|<span lang="en" dir="ltr" class="mw-content-ltr">This circumvents an intended security mechanism in bubblewrap, and allows all other software launched by steam, or running via steam-run to acquire these capabilities as well.</span>}}

{{file|/etc/nixos/configuration.nix|nix|3=programs.steam = let

patchedBwrap = pkgs.bubblewrap.overrideAttrs (o: {

patches = (o.patches or []) ++ [

./bwrap.patch

];

});

in {

enable = true;

package = pkgs.steam.override {

buildFHSEnv = (args: ((pkgs.buildFHSEnv.override {

bubblewrap = patchedBwrap;

}) (args // {

extraBwrapArgs = (args.extraBwrapArgs or []) ++ [ "--cap-add ALL" ];

})));

};

}}

{{file|/etc/nixos/bwrap.patch|diff|3=diff --git a/bubblewrap.c b/bubblewrap.c

index 8322ea0..4e20262 100644

--- a/bubblewrap.c

+++ b/bubblewrap.c

@@ -868,13 +868,6 @@ acquire_privs (void)

/* Keep only the required capabilities for setup */

set_required_caps ();

}

- else if (real_uid != 0 && has_caps ())

- {

- /* We have some capabilities in the non-setuid case, which should not happen.

- Probably caused by the binary being setcap instead of setuid which we

- don't support anymore */

- die ("Unexpected capabilities but not setuid, old file caps config?");

- }

else if (real_uid == 0)

{

/* If our uid is 0, default to inheriting all caps; the caller

}}

as an additional change, you may also need to replace Steam's own bwrap binary with a symbolic link to this modified bwrap binary, found at <code>~/.local/share/Steam/ubuntu12_32/steam-runtime/usr/libexec/steam-runtime-tools-0/srt-bwrap</code>.

</div>

Steam will periodically replace this modification with its own binary when steam-runtime updates, so you may need to re-apply this change if it breaks.

</div>

Line 268:

Line 314:

When launching wlx-overlay-s in SteamVR (or any OpenVR compositor) it will register an autostart manifest. Currently, this manifest will reference a Nix store path of wlx-overlay-s, which might get garbage collected after rebuilds of your NixOS/Nix profile. A workaround is to regularly run the following command to update the manifest's store path:{{Commands|

When launching wlx-overlay-s in SteamVR (or any OpenVR compositor) it will register an autostart manifest. Currently, this manifest will reference a Nix store path of wlx-overlay-s, which might get garbage collected after rebuilds of your NixOS/Nix profile. A workaround is to regularly run the following command to update the manifest's store path:

# Run wlx-overlay-s and replace any running instance

</div>

{{Commands|

# <span lang="en" dir="ltr" class="mw-content-ltr">Run wlx-overlay-s and replace any running instance</span>

$ wlx-overlay-s --replace}}

~~</div>~~

Line 279:

Line 327:

* [https://lvra.gitlab.io Linux VR Adventures Wiki]

</div>

[[Category:Video]]

[[Category:Hardware]]

@@ Line 78: / Line 78: @@
 For further information about available environment variables and tweaks, read the [https://lvra.gitlab.io/docs/fossvr/monado/ Linux VR Adventures wiki] and the [https://monado.freedesktop.org/getting-started.html#environment-variables Monado documentation about environment variables]
 </div>
 <div lang="en" dir="ltr" class="mw-content-ltr">
@@ Line 92: / Line 91: @@
 </div>
-<div lang="en" dir="ltr" class="mw-content-ltr">
+{{Warning|<span lang="en" dir="ltr" class="mw-content-ltr">Older versions of Proton will always query the current OpenVR and OpenXR runtime. If you use OpenComposite, and it fails to initialize an OpenXR context, Proton will fail to launch. A workaround is to delete the ~/.config/openvr/openvrpaths.vrpath file and then retry launching the game.</span>}}
-{{Warning|Older versions of Proton will always query the current OpenVR and OpenXR runtime. If you use OpenComposite, and it fails to initialize an OpenXR context, Proton will fail to launch. A workaround is to delete the ~/.config/openvr/openvrpaths.vrpath file and then retry launching the game.}}
-</div>
 <div lang="en" dir="ltr" class="mw-content-ltr">
@@ Line 143: / Line 140: @@
 </div>
-<div lang="en" dir="ltr" class="mw-content-ltr">
+{{Warning|<span lang="en" dir="ltr" class="mw-content-ltr">As of WiVRn version 0.23, WiVRn now manages the opencomposite paths itself. Only use the above opencomposite configuration when using versions below v0.23.</span>}}
-{{Warning|As of WiVRn version 0.23, WiVRn now manages the opencomposite paths itself. Only use the above opencomposite configuration when using versions below v0.23.}}
-</div>
 {{File|/etc/nixos/configuration.nix|nix|3=services.wivrn = {
@@ Line 215: / Line 210: @@
 </div>
-<div lang="en" dir="ltr" class="mw-content-ltr">
+{{Note|<span lang="en" dir="ltr" class="mw-content-ltr">Steam is run in a bubblewrap-based FHS environment. This environment runs Steam in a user namespace, which prevents it from using any capabilities or setuid binaries. This means that asynchronous reprojection can not be used on NixOS, without patching the kernel to remove these restrictions completely, or modifying the bubblewrap binary used for running Steam to remove these capability protections. Both of these workarounds come with their own security tradeoffs. See this [https://github.com/NixOS/nixpkgs/issues/217119 Nixpkgs issue]</span>}}
-{{Note|Steam is run in a bubblewrap-based FHS environment. This environment runs Steam in a user namespace, which prevents it from using any capabilities or setuid binaries. This means that asynchronous reprojection can not be used on NixOS, without patching the kernel to remove these restrictions completely. See this [https://github.com/NixOS/nixpkgs/issues/217119 Nixpkgs issue]}}
-</div>
 <div lang="en" dir="ltr" class="mw-content-ltr">
@@ Line 227: / Line 220: @@
 </div>
-<div lang="en" dir="ltr" class="mw-content-ltr">
+{{Warning|<span lang="en" dir="ltr" class="mw-content-ltr">This removes intentional restrictions from the kernel, and it could cause scheduling issues. While it has not been reported that it does cause issues, this should be considered an unsupported configuration.</span>}}
-{{Warning|This removes intentional restrictions from the kernel, and it could cause scheduling issues. While it has not been reported that it does cause issues, this should be considered an unsupported configuration.}}
-</div>
 <div lang="en" dir="ltr" class="mw-content-ltr">
@@ Line 253: / Line 244: @@
 <div lang="en" dir="ltr" class="mw-content-ltr">
 It is also possible to just patch amdgpu and build it as an out-of-tree module, as described in [[Linux_kernel#Patching_a_single_In-tree_kernel_module]]
+</div>
+<div lang="en" dir="ltr" class="mw-content-ltr">
+=== Patching bubblewrap to allow capabilities ===
+</div>
+<div lang="en" dir="ltr" class="mw-content-ltr">
+By modifying the bubblewrap binary used for running Steam, you can allow processes in that FHS environment to acquire capabilities. This removes the need for patching the kernel directly.
+</div>
+{{Warning|<span lang="en" dir="ltr" class="mw-content-ltr">This circumvents an intended security mechanism in bubblewrap, and allows all other software launched by steam, or running via steam-run to acquire these capabilities as well.</span>}}
+{{file|/etc/nixos/configuration.nix|nix|3=programs.steam = let
+  patchedBwrap = pkgs.bubblewrap.overrideAttrs (o: {
+    patches = (o.patches or []) ++ [
+      ./bwrap.patch
+    ];
+  });
+in {
+  enable = true;
+  package = pkgs.steam.override {
+    buildFHSEnv = (args: ((pkgs.buildFHSEnv.override {
+      bubblewrap = patchedBwrap;
+    }) (args // {
+      extraBwrapArgs = (args.extraBwrapArgs or []) ++ [ "--cap-add ALL" ];
+    })));
+  };
+};
+}}
+{{file|/etc/nixos/bwrap.patch|diff|3=diff --git a/bubblewrap.c b/bubblewrap.c
+index 8322ea0..4e20262 100644
+--- a/bubblewrap.c
++++ b/bubblewrap.c
+@@ -868,13 +868,6 @@ acquire_privs (void)
+       /* Keep only the required capabilities for setup */
+       set_required_caps ();
+     }
+-  else if (real_uid != 0 && has_caps ())
+-    {
+-      /* We have some capabilities in the non-setuid case, which should not happen.
+-         Probably caused by the binary being setcap instead of setuid which we
+-         don't support anymore */
+-      die ("Unexpected capabilities but not setuid, old file caps config?");
+-    }
+   else if (real_uid == 0)
+     {
+       /* If our uid is 0, default to inheriting all caps; the caller
+}}
+<div lang="en" dir="ltr" class="mw-content-ltr">
+as an additional change, you may also need to replace Steam's own bwrap binary with a symbolic link to this modified bwrap binary, found at <code>~/.local/share/Steam/ubuntu12_32/steam-runtime/usr/libexec/steam-runtime-tools-0/srt-bwrap</code>.
+</div>
+<div lang="en" dir="ltr" class="mw-content-ltr">
+Steam will periodically replace this modification with its own binary when steam-runtime updates, so you may need to re-apply this change if it breaks.
 </div>
@@ Line 268: / Line 314: @@
 <div lang="en" dir="ltr" class="mw-content-ltr">
-When launching wlx-overlay-s in SteamVR (or any OpenVR compositor) it will register an autostart manifest. Currently, this manifest will reference a Nix store path of wlx-overlay-s, which might get garbage collected after rebuilds of your NixOS/Nix profile. A workaround is to regularly run the following command to update the manifest's store path:{{Commands|
+When launching wlx-overlay-s in SteamVR (or any OpenVR compositor) it will register an autostart manifest. Currently, this manifest will reference a Nix store path of wlx-overlay-s, which might get garbage collected after rebuilds of your NixOS/Nix profile. A workaround is to regularly run the following command to update the manifest's store path:
-# Run wlx-overlay-s and replace any running instance
+</div>
+{{Commands|
+# <span lang="en" dir="ltr" class="mw-content-ltr">Run wlx-overlay-s and replace any running instance</span>
 $ wlx-overlay-s --replace}}
-</div>
 <div lang="en" dir="ltr" class="mw-content-ltr">
@@ Line 279: / Line 327: @@
 <div lang="en" dir="ltr" class="mw-content-ltr">
 * [https://lvra.gitlab.io Linux VR Adventures Wiki]
+</div>
+<div lang="en" dir="ltr" class="mw-content-ltr">
 [[Category:Video]]
 [[Category:Hardware]]