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-system-lock reports success when shell IPC never requests a lock
Reported by bigminer · filed Sep 2, 2026Closed upstream on 2026-09-02 by its own reporter bigminer, as not planned. Closed by its own reporter — not by itself evidence of a fix.
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
Description
During an automatic idle lock, omarchy-system-lock exited successfully, but
the Omarchy shell never requested or established a Wayland session lock. The
machine therefore remained unsecured until I restarted the compositor.
Expected behavior
After the idle lock timeout, either:
- the shell establishes a secure session lock, or
omarchy-system-lockreturns a failure that the idle service can report or retry.
Evidence
At 2026-09-01 21:54:41 CDT:
omarchy idle ... lock-system: lock-timeout
omarchy idle ... process-start: lock omarchy-system-lock
omarchy idle ... process-exit: lock exitCode=0 status=0
There were no intervening or subsequent lock-service messages:
lock-requested
lock-pending: screen-stabilizing
secure=true
These messages do appear during successful locks earlier in the same boot.
The compositor was manually stopped/restarted approximately two minutes later
to recover. There is no coredump for Omarchy Shell, Quickshell, or Hyprland.
Possible mechanism
omarchy-system-lock begins with:
omarchy-shell lock lock >/dev/null
The script does not use set -e or explicitly check that command's status. It
then runs other commands whose successful completion can make the overall script
exit 0 even if the shell IPC call failed.
This is an inference from the script and timeline; the original IPC error was
not preserved in the journal.
System
- Omarchy: 4.0.2-1
- Hyprland: 0.56.2-1
- Quickshell: 0.3.1-1
- Kernel: 7.1.9.arch1-2
- NVIDIA open driver: 610.57.04
- Idle configuration: screensaver 150 seconds, lock 300 seconds
ttfx: 0.3.2-1
Related but distinct
- #6628: shell exits after acquiring the lock; here the lock was never requested.
- #6684: shell exits on an invalid Wayland output; no shell exit occurred here.
Filed by GPT-5 via Codex.
View raw text
## Description
During an automatic idle lock, `omarchy-system-lock` exited successfully, but
the Omarchy shell never requested or established a Wayland session lock. The
machine therefore remained unsecured until I restarted the compositor.
## Expected behavior
After the idle lock timeout, either:
1. the shell establishes a secure session lock, or
2. `omarchy-system-lock` returns a failure that the idle service can report or retry.
## Evidence
At 2026-09-01 21:54:41 CDT:
omarchy idle ... lock-system: lock-timeout
omarchy idle ... process-start: lock omarchy-system-lock
omarchy idle ... process-exit: lock exitCode=0 status=0
There were no intervening or subsequent lock-service messages:
lock-requested
lock-pending: screen-stabilizing
secure=true
These messages do appear during successful locks earlier in the same boot.
The compositor was manually stopped/restarted approximately two minutes later
to recover. There is no coredump for Omarchy Shell, Quickshell, or Hyprland.
## Possible mechanism
`omarchy-system-lock` begins with:
omarchy-shell lock lock >/dev/null
The script does not use `set -e` or explicitly check that command's status. It
then runs other commands whose successful completion can make the overall script
exit 0 even if the shell IPC call failed.
This is an inference from the script and timeline; the original IPC error was
not preserved in the journal.
## System
- Omarchy: 4.0.2-1
- Hyprland: 0.56.2-1
- Quickshell: 0.3.1-1
- Kernel: 7.1.9.arch1-2
- NVIDIA open driver: 610.57.04
- Idle configuration: screensaver 150 seconds, lock 300 seconds
- `ttfx`: 0.3.2-1
## Related but distinct
- #6628: shell exits after acquiring the lock; here the lock was never requested.
- #6684: shell exits on an invalid Wayland output; no shell exit occurred here.
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
- Fixed bypr/9429· 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.