root/ubuntu-post-install
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(kyber-linux): correct login flow docs — Maxima loopback OAuth, not WebView2

Browse Source 
Kyber uses a PKCE loopback OAuth flow (Maxima): it starts a temporary
HTTP server on 127.0.0.1 and calls cmd /c start to open the EA auth URL
in the system browser. On native Linux, Wine's cmd passes http:// URLs
to xdg-open, which works fine inside Steam's single bwrap layer.

Remove the incorrect claim that WebView2 intercepts qrc:// URIs and is
the only path to completing login. Keep the WebView2 runtime install
(harmless, prevents in-app render errors) but clarify it is not the
login mechanism.

Update end-of-script instructions to describe what the user will actually
see: browser opens EA page, redirects to 127.0.0.1:PORT, tab shows OK or
connection-refused (normal), login completes in Kyber. Add troubleshooting
notes for the two real failure modes: xdg-open not reaching the desktop
(headless/no DISPLAY), and login timeout (loopback server expired).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01D8ckUJQtj1pH8jtAddBDZs
This commit is contained in:
Claude
2026-06-23 20:14:06 +00:00
parent 351bfc47e8
commit 5f61c7bad2
1 changed files with 47 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files
scripts/setup-kyber-linux.sh
+47 -34
View File
@@ -3,43 +3,46 @@
# native Linux Steam machine (headless or desktop) with Proton Experimental. # native Linux Steam machine (headless or desktop) with Proton Experimental.
# #
# Kyber is a community multiplayer client for Star Wars Battlefront II (2017) # Kyber is a community multiplayer client for Star Wars Battlefront II (2017)
# after EA shut down the official servers. It is a Windows app (Flutter/Rust) # after EA shut down the official servers. It is a Windows app (Flutter/Rust).
# with an embedded Microsoft Edge WebView2 used for its EA OAuth login flow.
# #
# ── Why this is the RIGHT place to run Kyber ─────────────────────────────── # ── How Kyber's EA login actually works ────────────────────────────────────
# #
# Kyber's login redirects to a qrc:// URI (a Qt-internal resource scheme) that # Kyber uses the "Maxima" OAuth PKCE flow:
# only its OWN embedded WebView2 can intercept. WebView2 therefore MUST work. # 1. Kyber starts a temporary HTTP server on 127.0.0.1 (dynamic port ~41413+)
# 2. It calls cmd /c start "" "<EA auth URL>" to open a browser
# 3. You log in on the EA page; EA redirects to 127.0.0.1:PORT/?code=...
# 4. Kyber's HTTP server catches the code and exchanges it for tokens
# #
# Inside a Wolf / Games-on-Whales Docker container, WebView2 cannot start: # On native Linux, Wine's built-in cmd.exe passes http(s):// URLs to
# Proton wraps Wine in bubblewrap (bwrap), and nesting that inside Docker # xdg-open, which launches your system browser. Steam's pressure-vessel
# blocks CLONE_NEWUSER, which WebView2's subprocess sandbox requires. The # (bwrap) sandbox does NOT block xdg-open on native Linux — xdg-open reaches
# result is endless login failures (see setup-kyber-wolf.sh for the gory # the host desktop and the browser opens normally.
# details and the fake-cmd.exe / Firefox workarounds that still cannot finish
# the flow because no external browser can handle qrc://).
# #
# On NATIVE Linux Steam there is only a single bwrap layer (Proton's own), # After you approve the EA login page the browser is redirected to
# which has enough namespace privilege for WebView2 to initialize. So here the # 127.0.0.1:PORT (Kyber's loopback server). The browser hits that address,
# login flow works as designed: Kyber opens its built-in browser, you log in # Kyber receives the auth code, and login completes. No special shims needed.
# to EA, EA redirects to qrc://, and Kyber's WebView2 catches the auth code.
# #
# No fake cmd.exe. No Firefox. No URL watcher. None of that scaffolding is # ── Why NOT to run Kyber inside Wolf / Games-on-Whales ─────────────────────
# needed here — it only existed to work around WebView2 being unable to start.
# #
# ── Do you still need WebView2? YES ──────────────────────────────────────── # Wolf runs Docker + Proton's bwrap nested. The double-sandbox blocks
# CLONE_NEWUSER which breaks WebView2, AND the inner bwrap prevents
# xdg-open from reaching the host display. Kyber's loopback redirect to
# 127.0.0.1:PORT also fails inside the container network stack. Use native
# Linux Steam instead — it's the supported path.
# #
# WebView2 is not the problem — it is the solution. It is the only component # ── WebView2 ───────────────────────────────────────────────────────────────
# that can complete Kyber's EA OAuth login. This script makes sure the #
# WebView2 Evergreen RUNTIME (not just the bootstrapper stub) is actually # WebView2 is NOT required for the login flow (Maxima handles that). This
# installed in Kyber's Wine prefix. If only the stub is present, Kyber falls # script still installs the WebView2 Evergreen runtime because Kyber may use
# back to `cmd /c start <url>` and login fails even on native Linux. # it for in-app content rendering. Installing it causes no harm and prevents
# any fallback-related error dialogs inside Kyber.
# #
# ── Headless note ────────────────────────────────────────────────────────── # ── Headless note ──────────────────────────────────────────────────────────
# #
# On a headless GPU box you do not need Wolf to stream. Use Steam Remote Play: # On a headless GPU box use Steam Remote Play: install Steam, configure a
# install Steam, set up a virtual display so Steam has something to render to, # virtual/dummy display so Steam has something to render to, add Kyber +
# add Kyber + SWBF2, then connect with the Steam Link app from any device. # SWBF2, then connect with the Steam Link app from any device.
# This script sets up a dummy/virtual X display if no display is detected. # This script warns if no display is detected at setup time.
# #
# ── Prerequisites ────────────────────────────────────────────────────────── # ── Prerequisites ──────────────────────────────────────────────────────────
# a. Steam installed and launched at least once (native, not Flatpak ideally # a. Steam installed and launched at least once (native, not Flatpak ideally
@@ -318,18 +321,28 @@ echo ""
echo "Next steps:" echo "Next steps:"
echo " 1. RESTART Steam so it picks up the new shortcut and compat mapping." echo " 1. RESTART Steam so it picks up the new shortcut and compat mapping."
echo " 2. Launch 'Kyber Launcher' from your Steam Library." echo " 2. Launch 'Kyber Launcher' from your Steam Library."
echo " 3. Click Login. Kyber's embedded WebView2 opens the EA login page." echo " 3. Click Login. Kyber starts a temporary server on 127.0.0.1 and"
echo " 4. Log in to EA (Steam / email / 2FA as usual)." echo " calls xdg-open to open the EA login page in your system browser."
echo " 5. EA redirects to qrc://login_successful — WebView2 catches the code" echo " 4. Log in on the EA page (email / Steam / 2FA as usual)."
echo " INTERNALLY and completes the token exchange. No browser, no qrc" echo " 5. EA redirects back to 127.0.0.1:<port>/?code=... — Kyber's"
echo " error, no manual step. This is the whole point of running natively." echo " loopback server catches the auth code and login completes."
echo " The browser tab will show a plain 'OK' or a connection-refused"
echo " message once the code is consumed — that is normal."
echo "" echo ""
echo "Streaming from a headless box:" echo "Streaming from a headless box:"
echo " Use Steam Remote Play — install the Steam Link app on your client," echo " Use Steam Remote Play — install the Steam Link app on your client,"
echo " it discovers this host over your network. No Wolf, no Moonlight, no" echo " it discovers this host over your network. No Wolf, no Moonlight, no"
echo " VPN required for a single user." echo " VPN required for a single user."
echo "" echo ""
echo "If login still falls back to a cmd error:" echo "If the EA login page never opens:"
echo " WebView2 didn't initialize. Confirm the runtime exists:" echo " xdg-open failed to reach your desktop. Make sure a display is set:"
echo " export DISPLAY=:0 (or WAYLAND_DISPLAY=wayland-0, etc.)"
echo " Then relaunch Kyber from that terminal."
echo ""
echo "If the browser opens but login redirects back to the EA sign-in page:"
echo " Kyber's loopback server timed out. Log in faster, or close and"
echo " reopen Kyber to get a fresh loopback server before clicking Login."
echo ""
echo "If WebView2 errors appear inside Kyber (not the login flow):"
echo " find \"$KYBER_PFX/pfx/drive_c\" -iname msedgewebview2.exe" echo " find \"$KYBER_PFX/pfx/drive_c\" -iname msedgewebview2.exe"
echo " If missing, re-run the WebView2 install step shown above." echo " If missing, re-run the WebView2 install step shown above."