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.
Crash watcher reports normal 1Password window close as a crash
Reported by seanfreiburg · filed Aug 22, 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
What happened
After installing and opening 1Password, I closed its window using Super+W. Omarchy immediately displayed:
Process crashed: 1password
The close was intentional and the 1Password log shows an orderly shutdown.
Expected
Closing 1Password normally should not produce a critical crash notification.
Evidence
System:
- Omarchy 4.0.0-1
- Hardware: Apple MacBook Pro (MacBookPro18,2), ARM64
- 1Password 8.12.0 ARM64
The 1Password log immediately before systemd-coredump recorded the event:
Front end event: window closed
Front end event: app will quit
shutdown requested!
starting app shutdown
running shutdown hook...
Failed to prepare for requesting dumpsystemd-coredump then recorded:
Process: 1password
Signal: SIGTRAP
si_code: TRAP_BRKPT
Core file: none
Resource limits disable core dumping for processThere was no memory pressure or OOM kill. The app had synced successfully before being closed.
Likely mechanism
omarchy-crash-watch announces every journal entry with the systemd-coredump message ID. It currently cannot distinguish this 1Password shutdown-time Crashpad SIGTRAP from an unexpected application crash.
This differs from #7785: that report involves a background 1password --lock helper across suspend/resume. This report concerns closing the main GUI normally with Super+W.
Reproduction
- Launch 1Password 8.12.0 on ARM64.
- Close its window using Super+W.
- Observe the critical “Process crashed: 1password” notification.
Filed by GPT-5 via Codex.
View raw text
## What happened After installing and opening 1Password, I closed its window using Super+W. Omarchy immediately displayed: > Process crashed: 1password The close was intentional and the 1Password log shows an orderly shutdown. ## Expected Closing 1Password normally should not produce a critical crash notification. ## Evidence System: - Omarchy 4.0.0-1 - Hardware: Apple MacBook Pro (MacBookPro18,2), ARM64 - 1Password 8.12.0 ARM64 The 1Password log immediately before systemd-coredump recorded the event: ```text Front end event: window closed Front end event: app will quit shutdown requested! starting app shutdown running shutdown hook... Failed to prepare for requesting dump ``` systemd-coredump then recorded: ```text Process: 1password Signal: SIGTRAP si_code: TRAP_BRKPT Core file: none Resource limits disable core dumping for process ``` There was no memory pressure or OOM kill. The app had synced successfully before being closed. ## Likely mechanism `omarchy-crash-watch` announces every journal entry with the systemd-coredump message ID. It currently cannot distinguish this 1Password shutdown-time Crashpad SIGTRAP from an unexpected application crash. This differs from #7785: that report involves a background `1password --lock` helper across suspend/resume. This report concerns closing the main GUI normally with Super+W. ## Reproduction 1. Launch 1Password 8.12.0 on ARM64. 2. Close its window using Super+W. 3. Observe the critical “Process crashed: 1password” notification. 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
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 08:24 UTC