Project Chimera
Меню

Исходники

73 строк · 5 КиБ

docs/BROWSER-REPAIR-2026-10-11.md

1# Browser and diagnostic report repair, 11 October 2026
2
3The installed 0.2.2 bundle loaded its own WebKit library but started the
4system WebKit subprocesses. NetworkProcess aborted with
5`Received invalid message: 'NetworkProcess_AllowFileAccessFromWebProcessReply'`.
6
7The installer now patches the helper path with byte-oriented matching,
8uses the current user's private logind runtime directory when
9`XDG_RUNTIME_DIR` is absent, and fails if relocation cannot be verified.
10It requires an existing runtime directory owned by the current user with
11mode 0700. The runtime and installer calculate the same helper symlink.
12No sandbox settings changed.
13
14Web views use WebBrowser caching. Downloads preserve existing files and
15show completion/failure; a download's policy interruption no longer
16displays a site failure. Diagnostic collection runs outside the GTK
17thread. The report picker retains its parent window even when animations
18are disabled, and redaction placeholders render as literal text.
19
20Lampa defaults to direct TMDB access only when no proxy preference exists.
21On this host the CUB proxy repeatedly waited for 10-second timeouts;
22the direct source delivered 28 cards and posters within 4.3 seconds in
23the network comparison. Existing explicit proxy preferences are retained.
24
25MangoHud is enabled in the registry defaults. Existing explicit per-game
26choices still override it; the clean launch mode remains available.
27`appearance.toml` supports `large_logo = true` (default false) for the full
2864px emblem on the left, with Chimera/Launcher on two lines to the right.
29Runtime switching is available on the appearance page.
30The earlier HOST_LC_ALL fix from 31d5469 is preserved in this local build.
31
32Checks: 1561 workspace tests passed, 17 ignored; Clippy with `-D warnings`;
33three installer regression tests; release build; all 20 application pages
34opened in an isolated real GTK session. Browser navigation, bookmarks,
35downloads and report preview/send were exercised through the UI.
36Game launching, store purchases and film playback were not
37exercised in this repair session.
38
39Follow-up: Epic's Cloudflare login challenge still failed inside WebKit.
40The owner confirmed the same challenge passes manually in normal Chrome.
41The owner then completed the external-browser authorizationCode flow in
42the installed Launcher. The credential file is nonempty with mode 0600;
43two independent installed CLI processes refreshed the real session
44successfully (0.55s and 0.48s), without requesting another login.
45Each store and browser toolbar now offers opening its current HTTP(S)
46page in the system browser. Epic's login banner opens normal-browser
47authentication; the Accounts page presents that path first, followed by
48the one-time code field. Embedded authentication remains an optional path.
49Epic now defaults to a native page: the storefront opens in the system
50browser's existing profile, while the Launcher account uses the saved
51refresh token for library/install access. Paste the authorizationCode
52once; later API access refreshes and persists the rotated token.
53The manual exchange runs on a worker and prevents duplicate submission.
54Successful OAuth responses persist the rotated token before optional
55Legendary synchronization. Legendary authentication has a 30-second
56process deadline; errors/timeouts preserve the Launcher session.
57The embedded storefront remains an explicitly expanded optional path;
58no Epic WebView is created by default. Existing cookies are preserved.
59Website and Launcher account sessions remain separate; cookies and
60challenge tokens are not copied between browsers. See
61[Cloudflare browser support](https://developers.cloudflare.com/cloudflare-challenges/reference/supported-browsers/).
62
63The public report backend was blocked by OpenProject's ingress policy.
64GitOps c9dca34 permits only d8-system/chimera-compat on TCP 8080.
65Report 8 reached OpenProject 469 from the UI; queued report 7 retried and
66reached OpenProject 471. No report/database was deleted or restarted.
67
68Local rollback: close only Launcher through its tray, restore the saved
69app and the two modified configuration files, run the restored relocate
70script, then reopen Launcher. Preserve game progress and credentials.
71Revert c9dca34 in the GitOps repository only if undoing the network repair
72is required; doing so blocks diagnostic delivery again.
73