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.
Chromium crashes (SIGTRAP) on normal desktop launch — flags duplicated 2-3x from chromium-flags.conf
Reported by zaid-kamil · filed Sep 11, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #8394 (R-1420). GitHub close reason: completed.
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?
- Not yet mapped to any requirement or component.
- 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?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
System details
- Omarchy: 4.0.2-1
- Kernel: Linux 7.1.x-arch1
- Hyprland: (Omarchy default)
- Chromium: 152.0.7977.82-1
- Install date: 2026-09-11 17:44 IST
What's wrong?
Chromium crashes with SIGTRAP (si_code: SI_KERNEL) within seconds of a normal
desktop launch. The coredump reveals that flags from chromium-flags.conf are
being duplicated 2-3 times in the command line passed to the process:
chromium \
--ozone-platform=wayland \
--ozone-platform-hint=wayland \ # ×2
--load-extension=.../copy-url,.../yt-dlp,.../whatsapp-slim \ # ×3
--oauth2-client-id=... \ # ×2
--oauth2-client-secret=... # ×2The system-wide /usr/share/omarchy/config/chromium-flags.conf defines these
flags once. Chromium itself reads this file at startup via the Arch wrapper.
Something in the launch chain is also injecting the same flags, causing
duplication. Chromium's flag parser hits an internal assertion on the repeated--load-extension (or repeated --oauth2-client-*) and executes int3.
Evidence
- Signal: SIGTRAP,
si_code: SI_KERNEL— process self-inflicted trap - Timing: Crash occurs ~8 seconds after launch, during ChromeMain init
- Pattern: 7 Chromium SIGTRAP crashes in one day (3 in a row at 17:40,
then 4 in a row at 20:47-20:54), all with the same duplicated flag set
- Not OOM: 4.4 GiB available, 25 GiB swap free
- Not GPU-specific: Launching without the duplicated flags (tested by
btownsend in #8394) works fine
- User data intact: Session restore works, no data lost
How to reproduce
- Stock Omarchy install with default
chromium-flags.confand
omarchy-install-chromium-google-account (adds OAuth flags)
2. Launch Chromium normally from the desktop/launcher
3. Observe SIGTRAP crash; check coredumpctl info <pid> to see duplicated flags
What's different from existing issues
- #11085 reports headless/Playwright invocations crashing because flags are
force-injected. Our crash is a normal desktop launch — the flags are
duplicated, not conflicting with headless flags.
- #8394 reports OAuth popup processes crashing on Hyprland. Our crash
happens during normal browsing, not just OAuth flows. The btownsend
comment identifies --oauth2-client-* as the common factor, but our
command line also shows --load-extension tripled, suggesting a broader
flag-injection duplication issue.
Expected behavior
chromium-flags.conf should be applied exactly once. Normal desktop launches
should not crash.
Filed by Claude Sonnet 4.5 via Claude Code.
View raw text
## System details - Omarchy: 4.0.2-1 - Kernel: Linux 7.1.x-arch1 - Hyprland: (Omarchy default) - Chromium: 152.0.7977.82-1 - Install date: 2026-09-11 17:44 IST ## What's wrong? Chromium crashes with SIGTRAP (`si_code: SI_KERNEL`) within seconds of a normal desktop launch. The coredump reveals that flags from `chromium-flags.conf` are being **duplicated 2-3 times** in the command line passed to the process: ``` chromium \ --ozone-platform=wayland \ --ozone-platform-hint=wayland \ # ×2 --load-extension=.../copy-url,.../yt-dlp,.../whatsapp-slim \ # ×3 --oauth2-client-id=... \ # ×2 --oauth2-client-secret=... # ×2 ``` The system-wide `/usr/share/omarchy/config/chromium-flags.conf` defines these flags once. Chromium itself reads this file at startup via the Arch wrapper. Something in the launch chain is also injecting the same flags, causing duplication. Chromium's flag parser hits an internal assertion on the repeated `--load-extension` (or repeated `--oauth2-client-*`) and executes `int3`. ## Evidence - **Signal:** SIGTRAP, `si_code: SI_KERNEL` — process self-inflicted trap - **Timing:** Crash occurs ~8 seconds after launch, during ChromeMain init - **Pattern:** 7 Chromium SIGTRAP crashes in one day (3 in a row at 17:40, then 4 in a row at 20:47-20:54), all with the same duplicated flag set - **Not OOM:** 4.4 GiB available, 25 GiB swap free - **Not GPU-specific:** Launching without the duplicated flags (tested by btownsend in #8394) works fine - **User data intact:** Session restore works, no data lost ## How to reproduce 1. Stock Omarchy install with default `chromium-flags.conf` and `omarchy-install-chromium-google-account` (adds OAuth flags) 2. Launch Chromium normally from the desktop/launcher 3. Observe SIGTRAP crash; check `coredumpctl info <pid>` to see duplicated flags ## What's different from existing issues - **#11085** reports headless/Playwright invocations crashing because flags are force-injected. Our crash is a **normal desktop launch** — the flags are duplicated, not conflicting with headless flags. - **#8394** reports OAuth popup processes crashing on Hyprland. Our crash happens during **normal browsing**, not just OAuth flows. The btownsend comment identifies `--oauth2-client-*` as the common factor, but our command line also shows `--load-extension` tripled, suggesting a broader flag-injection duplication issue. ## Expected behavior `chromium-flags.conf` should be applied exactly once. Normal desktop launches should not crash. --- Filed by Claude Sonnet 4.5 via Claude Code.
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
- Related PRpr/11907· confirmed
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.
No decision has been recorded yet.