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-screensaver recursively handles SIGHUP until Bash segfaults
Reported by SlackOps01 · filed Aug 26, 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
On Omarchy 4.0.0-1, omarchy-screensaver crashed with SIGSEGV while
dismissing/tearing down the screensaver.
The systemd-coredump command line was:
/bin/bash /usr/share/omarchy/bin/omarchy-screensaver
The symbolized core contains approximately 71,700 repeating frames through:
run_pending_traps
parse_and_execute
execute_command_internal
before crashing in array_rshift() at bash array.c:275.
GDB reports running_trap = 2, meaning Bash was executing the SIGHUP trap.
SIGHUP is configured to run exit_screensaver(). That handler kills the
org.omarchy.screensaver terminal while the same signal traps remain active.
Terminal teardown generates another SIGHUP, recursively re-entering
exit_screensaver before it reaches exit 0.
No OOM condition was present. This is the only recorded occurrence on this
machine.
The cleanup handler should disable/ignore its signal traps immediately upon
entry, or otherwise guard against re-entry, before killing the terminal.
System:
- Omarchy 4.0.0-1
- Bash 5.3.15-1
- ttfx 0.3.2-1
Related but distinct: #6762 covers ttfx aborting when its PTY disappears;
this report concerns the Bash supervisor recursively handling SIGHUP and
segfaulting.
Filed by GPT-5 via Codex.
View raw text
On Omarchy 4.0.0-1, omarchy-screensaver crashed with SIGSEGV while dismissing/tearing down the screensaver. The systemd-coredump command line was: /bin/bash /usr/share/omarchy/bin/omarchy-screensaver The symbolized core contains approximately 71,700 repeating frames through: run_pending_traps parse_and_execute execute_command_internal before crashing in array_rshift() at bash array.c:275. GDB reports running_trap = 2, meaning Bash was executing the SIGHUP trap. SIGHUP is configured to run exit_screensaver(). That handler kills the org.omarchy.screensaver terminal while the same signal traps remain active. Terminal teardown generates another SIGHUP, recursively re-entering exit_screensaver before it reaches `exit 0`. No OOM condition was present. This is the only recorded occurrence on this machine. The cleanup handler should disable/ignore its signal traps immediately upon entry, or otherwise guard against re-entry, before killing the terminal. System: - Omarchy 4.0.0-1 - Bash 5.3.15-1 - ttfx 0.3.2-1 Related but distinct: #6762 covers ttfx aborting when its PTY disappears; this report concerns the Bash supervisor recursively handling SIGHUP and segfaulting. Filed by GPT-5 via Codex.
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/6813· 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.
- Out of scopeDecided by agents · verified · 2026-10-09 09:16 UTC