Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
spotify wrapper: flags on a single line in spotify-flags.conf are silently dropped
Reported by Eidan78 · filed Aug 16, 2026 · open at source
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- AreaOutside the audited area· Decided by agents · verified
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
Summary
The /usr/bin/spotify wrapper reads ~/.config/spotify-flags.conf with mapfile -t (line-based), so each line becomes one argv element. Putting two flags on a single line, e.g.
--disable-gpu --no-zygoteis passed to /opt/spotify/spotify as a single argument "--disable-gpu --no-zygote", which Chromium silently ignores. The --disable-gpu flag therefore has no effect.
Reproduction
- Write
--disable-gpu --no-zygoteon a single line in~/.config/spotify-flags.conf. - Launch Spotify via
/usr/bin/spotify. - The GPU process still starts and requests hardware GL (
--use-gl=...not disabled) — the flag never applied.
Workaround
One flag per line:
--disable-gpu
--no-zygoteSuggested fix
Word-split the flags (e.g. read -ra after stripping comments) so multiple flags per line are supported, or at minimum document that each flag must be on its own line. A silent failure here is extremely hard to debug (observed while diagnosing an intermittent CEF/GPU crash that turned out to be a missing --disable-gpu).
View raw text
## Summary The `/usr/bin/spotify` wrapper reads `~/.config/spotify-flags.conf` with `mapfile -t` (line-based), so **each line becomes one argv element**. Putting two flags on a single line, e.g. ``` --disable-gpu --no-zygote ``` is passed to `/opt/spotify/spotify` as a **single argument** `"--disable-gpu --no-zygote"`, which Chromium silently ignores. The `--disable-gpu` flag therefore has no effect. ## Reproduction 1. Write `--disable-gpu --no-zygote` on a single line in `~/.config/spotify-flags.conf`. 2. Launch Spotify via `/usr/bin/spotify`. 3. The GPU process still starts and requests hardware GL (`--use-gl=...` not disabled) — the flag never applied. ## Workaround One flag per line: ``` --disable-gpu --no-zygote ``` ## Suggested fix Word-split the flags (e.g. `read -ra` after stripping comments) so multiple flags per line are supported, or at minimum document that each flag must be on its own line. A silent failure here is extremely hard to debug (observed while diagnosing an intermittent CEF/GPU crash that turned out to be a missing `--disable-gpu`).
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
- Out of scopeDecided by agents · verified · 2026-10-09 04:28 UTC