1.6.0

Fixes the blank white window on Linux

The desktop app opened a window that rendered nothing. It looked healthy from the outside — the core sidecar booted, the health check passed, the page reported as loaded — because the failure was in the renderer process, which died the instant the page loaded and left the empty window frame behind.

The cause was --no-sandbox. It tears down Chromium's sandbox entirely, and an unsandboxed renderer allocates its own shared memory instead of having the browser process broker it. On some kernels that allocation fails and Chromium aborts on a fatal CHECK(), killing the renderer with no error surfaced anywhere.

Chromium's own message blamed /dev/shm permissions; that was a red herring — it reproduced on a host whose /dev/shm was mode 1777 with 31 GB free.

The app now passes --disable-setuid-sandbox, which skips only the setuid chrome-sandbox helper that AppImage genuinely cannot support, while keeping the namespace sandbox that brokers shared memory correctly.

Also in this release

• Renderer crashes are now reported. A dead renderer used to present as a blank white rectangle with nothing logged. It now surfaces the crash reason and exit code, and shows a dialog rather than an empty window.
• A broken output stream can no longer take down the app. An unhandled EPIPE while relaying core logs would kill the main process with a modal "A JavaScript error occurred" dialog — reachable from a double-clicked AppImage with no terminal attached.
• Removed a pile of untested Linux launch switches, including an inverted Wayland/X11 check that only ever applied X11 to sessions already running X11.

Full Changelog: 1.5.0...1.6.0