Skip to content

fix: stop appending sandbox switches after startup - #1007

Open
OneNoted wants to merge 1 commit into
Mastermindzh:developfrom
OneNoted:fix/linux-sandbox-startup
Open

fix: stop appending sandbox switches after startup#1007
OneNoted wants to merge 1 commit into
Mastermindzh:developfrom
OneNoted:fix/linux-sandbox-startup

Conversation

@OneNoted

@OneNoted OneNoted commented Sep 6, 2026

Copy link
Copy Markdown

I've hit this on three Arch machines using Wayland, with Niri and Hyprland. With a fresh profile, TIDAL opens a blank player and child processes crash.

On this machine I'm running kernel 7.2.2-arch1-1, TIDAL Hi-Fi 8.1.3, and Castlabs Electron 43.0.0+wvcus. I reproduced it with both AUR packages (tidal-hifi-bin and tidal-hifi-git) and from source.

TIDAL appends no-sandbox and disable-seccomp-filter-sandbox after Electron has started its Linux zygotes. This appears to leave processes with inconsistent sandbox state.

This removes those late switches and keeps the saved setting using the existing renderer sandbox preferences. Passing --no-sandbox at launch still works. The settings text and troubleshooting docs explain the distinction.

Lint and the package build pass. I tested source and packaged builds with the renderer sandbox setting on and off. After clearing the local profile and caches, the patched build downloaded Widevine and loaded the TIDAL home page without new crashes. Signed-in playback also works. I haven't tested other operating systems.

@sonarqubecloud

sonarqubecloud Bot commented Sep 6, 2026

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant