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