mirror of
https://github.com/saphid/frame-control.git
synced 2026-10-06 06:00:33 +02:00
saphidandClaude Opus 5.5
2544255825
chromium-xr.sh steam adds a non-Steam shortcut through Steam's DevTools port. Chrome's flags move into frame/chromium-xr/launch.sh, which both the shortcut and launch run. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
28 lines
1.2 KiB
Bash
Executable File
28 lines
1.2 KiB
Bash
Executable File
#!/bin/bash
|
|
# Frame-side: start the WebXR Chromium build (~/chromium-xr). The Steam
|
|
# library shortcut "Chromium XR" runs this, and so does
|
|
# `scripts/chromium-xr.sh launch` (which adds a DevTools port). Extra
|
|
# arguments go to Chrome, so a URL opens that page.
|
|
#
|
|
# Lives in ~/Applications/ChromiumXR, outside ~/chromium-xr, so reinstalling
|
|
# the build doesn't delete it.
|
|
set -euo pipefail
|
|
|
|
CHROME="$HOME/chromium-xr/chrome"
|
|
[[ -x "$CHROME" ]] || { echo "launch.sh: no build at $CHROME (run chromium-xr.sh install)" >&2; exit 1; }
|
|
|
|
# Without --no-first-run and --password-store=basic, startup can stop at a
|
|
# first-run or keyring prompt.
|
|
# --disable-seccomp-filter-sandbox: under the XR seccomp policy, SteamVR's
|
|
# client reads /proc/self/status through the file broker, gets the broker's
|
|
# pid, and SteamVR binds the app to the wrong process, so xrCreateInstance
|
|
# fails. The namespace sandbox stays on, but seccomp is off for every
|
|
# process, so keep this profile for VR sites.
|
|
exec "$CHROME" \
|
|
--user-data-dir="$HOME/.config/chromium-xr" \
|
|
--enable-features=OpenXR \
|
|
--ozone-platform=x11 \
|
|
--no-first-run --no-default-browser-check --password-store=basic \
|
|
--disable-seccomp-filter-sandbox \
|
|
"$@"
|