Plan
Premium
Country
United Kingdom
Device
Desktop PC (AMD Ryzen 9950X3D, Radeon RX 7800 XT)
Operating System
Arch Linux, kernel 7.1.5-zen1-2-zen (x86_64), Wayland/sway 1.12
My Question or Issue
**Regression.** 1.2.90.451 works; 1.2.92.147 fails. Both bundle the same CEF
(`Chrome/146.0.7680.179`).
## Summary
On 1.2.92.147 the client opens a window that paints only its base colour `rgb(18,18,18)` plus the `…` overflow button. The renderer's React root (`#main`) stays **empty** and the app never retries.
The console shows:
```
BootstrapTimeoutError: Platform dependencies did not resolve within 15000ms
Failed to load resource: net::ERR_TIMED_OUT https://apresolve.spotify.com/?type=dealer-g2&type=spclient
```
(sometimes `net::ERR_SOCKET_NOT_CONNECTED` instead of `ERR_TIMED_OUT`), followed by `Uncaught Error: useUBILogger must be used within a <UBILoggerContextProvider>` which looks like a downstream effect of bootstrap never completing(?)
That `apresolve` request fails *while the TCP connection and TLS data
transfer visibly succeed on the wire.* Roughly 30 s after launch the identical request
succeeds in ~30 ms, and reloading the web view renders the full UI!
## Regression info
| Build | Source | Result |
|---|---|---|
| **1.2.90.451.gb094aab0** | snap revision 96 | **renders, 3/3 runs** |
| **1.2.92.147.g5b8f9367** | snap revision 97 | **blank, 3/3 runs** |
| 1.2.92.147.g5b8f9367 | AUR package | blank, 3/3 runs |
All comparisons used isolated `--user-data-dir` profiles, no extra flags, same account,
same machine, same network, minutes apart.
## Ruled out
Each tested individually on the failing build; all still blank:
- **GPU/driver/compositing**: `--disable-gpu` (pure software) also blank; no GPU resets in `dmesg`; GL accelerated
- **Xwayland vs native Wayland**: `--ozone-platform=wayland` identical
- **Caches**: cleared `GrShaderCache`, `ShaderCache`, `GraphiteDawnCache`, `Code Cache`
- **Profile**: fresh `--user-data-dir`
- **Credentials**: stripped `autologin.*`, logged in fresh; still blank
- **QUIC**: `--disable-quic`
- **DNS**: `--disable-features=AsyncDns`, `--dns-over-https-mode=off`; also verified the
local resolver returns correct answers for every Spotify endpoint
- **Address family**: tested with IPv6 disabled, IPv6 fully working, and every Spotify host pinned to IPv4 literals via `--host-resolver-rules`; no difference
- **fontconfig**: the bundled fontconfig (0x2011001) rejects this system's newer caches
(2.18.2); `FONTCONFIG_NO_CHECK_CACHE_VERSION=1` silenced the warning but did not help
- **D-Bus environment**: `gnome-keyring-daemon` owns `org.freedesktop.secrets`;
`xdg-desktop-portal`, `-gtk`, `-wlr` all running
- **Environment variables**: `env -i` with a minimal set
- **Not Chromium-wide**: plain `chromium` on the same host, fresh profile, has *no* startup stall (first fetch 1403 ms, then 3–13 ms). Only Spotify exhibits it.
