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.
omarchy-launch-browser causes Brave SIGTRAP when man is unavailable
Reported by johanthoren · filed Aug 29, 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
Description
omarchy-launch-browser runs the selected browser with --help to detect
Mozilla-based browsers:
if $browser_exec --help 2>/dev/null | grep -q MOZ_LOG; then
On Linux, Chromium-family browsers implement --help by executing man.
When man is unavailable, Brave calls PLOG(FATAL), raises SIGTRAP, and
systemd-coredump records a browser crash. Omarchy then launches the actual
browser successfully.
Steps to reproduce
- Use Brave as the default browser on a system without
man. - Run
omarchy-launch-browser. - Inspect
coredumpctl list brave.
The failing command can be reproduced without writing a core:
prlimit --core=0 -- /usr/bin/brave --help
Output:
[FATAL:chrome/app/chrome_main_delegate.cc:404] execlp failed:
No such file or directory (2)
Exit status: 133.
Expected behavior
The browser launches without executing a probe that crashes or creates a
systemd-coredump entry.
Actual behavior
Each launch creates a Brave SIGTRAP coredump from the --help probe. The real
browser starts afterward.
Three identical crashes were recorded on the same boot. Each command line ended
in --help, and each had the same stack offsets.
Versions
Omarchy: 4.0.1-1
Brave package: brave-bin 1:1.94.117-1
Architecture: aarch64
Suggested direction
Identify Mozilla-based browsers without executing the browser's --help
handler.
Filed by openai-codex/gpt-5.6-sol via Oh My Pi coding harness.
View raw text
## Description
`omarchy-launch-browser` runs the selected browser with `--help` to detect
Mozilla-based browsers:
if $browser_exec --help 2>/dev/null | grep -q MOZ_LOG; then
On Linux, Chromium-family browsers implement `--help` by executing `man`.
When `man` is unavailable, Brave calls PLOG(FATAL), raises SIGTRAP, and
systemd-coredump records a browser crash. Omarchy then launches the actual
browser successfully.
## Steps to reproduce
1. Use Brave as the default browser on a system without `man`.
2. Run `omarchy-launch-browser`.
3. Inspect `coredumpctl list brave`.
The failing command can be reproduced without writing a core:
prlimit --core=0 -- /usr/bin/brave --help
Output:
[FATAL:chrome/app/chrome_main_delegate.cc:404] execlp failed:
No such file or directory (2)
Exit status: 133.
## Expected behavior
The browser launches without executing a probe that crashes or creates a
systemd-coredump entry.
## Actual behavior
Each launch creates a Brave SIGTRAP coredump from the `--help` probe. The real
browser starts afterward.
Three identical crashes were recorded on the same boot. Each command line ended
in `--help`, and each had the same stack offsets.
## Versions
Omarchy: 4.0.1-1
Brave package: brave-bin 1:1.94.117-1
Architecture: aarch64
## Suggested direction
Identify Mozilla-based browsers without executing the browser's `--help`
handler.
Filed by openai-codex/gpt-5.6-sol via Oh My Pi coding harness.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 02:21 UTC