From 95efd18b73fd7792973efdee8761c73e6e39aace Mon Sep 17 00:00:00 2001 From: Ryan Houdek Date: Tue, 31 May 2022 17:12:08 -0700 Subject: [PATCH] AppConfig: Inject --no-sandbox in to steamwebhelper Steam's webhelper has started enabling its sandbox which completely breaks under FEX since we don't support seccomp. Curiously the Chromium code is actually supposed to support a fallback namespace only mode, which is used in glibc 2.34 environments. The startup script for this will try to use this namespace only mode, but Chromium developers never tested this in an environment that doesn't support seccomp. Due to an early check in their sandbox code, it checks for bpf support before checking for which sandbox mode it is entering. This returns early with a false statement which brings the entire browser instance down with an assert. Inject the --no-sandbox argument so we get around this and the sandbox is disabled. --- Data/AppConfig/steamwebhelper.json | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 Data/AppConfig/steamwebhelper.json diff --git a/Data/AppConfig/steamwebhelper.json b/Data/AppConfig/steamwebhelper.json new file mode 100644 index 000000000..2ee466f36 --- /dev/null +++ b/Data/AppConfig/steamwebhelper.json @@ -0,0 +1,5 @@ +{ + "Config": { + "AdditionalArguments": "--no-sandbox" + } +}