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.
system-power-test.sh invokes the real Omarchy OSD
Reported by wadewegner · filed Aug 15, 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
System details
- Omarchy 4.0.0-1 (Quattro)
- Hyprland 0.56.2
- Quickshell 0.3.0 (revision
28771c7c74b42e20afca0b1b63980cb46515537c) - Linux 7.1.8-arch1-3
- Intel Core i7-9700, Intel UHD 630, NVIDIA GTX 1660 Ti
What's wrong?
I ran the power test on a live Omarchy Quattro desktop:
bash test/shell.d/system-power-test.shThe test passed, but it displayed the real “Rebooting” OSD followed by the real “Shutting down” OSD. The last one remained visible after the test.
No real reboot or poweroff occurred. The test safely stubs systemd-run, along with omarchy-state, omarchy-hyprland-window-close-all, and sleep.
It does not stub omarchy-osd. Because the test invokes the real bin/omarchy-system-reboot and bin/omarchy-system-shutdown scripts, those commands reach the active Omarchy shell and create a real OSD on the developer's desktop.
The fix should be pretty simple: add omarchy-osd to the test stubs and assert these calls in the existing call log:
omarchy-osd -i reboot -m Rebooting -d 5000
omarchy-osd -i shutdown -m Shutting down -d 5000That preserves the current coverage, verifies the OSD behavior, and keeps the test from changing the active desktop.
View raw text
### System details - Omarchy 4.0.0-1 (Quattro) - Hyprland 0.56.2 - Quickshell 0.3.0 (revision `28771c7c74b42e20afca0b1b63980cb46515537c`) - Linux 7.1.8-arch1-3 - Intel Core i7-9700, Intel UHD 630, NVIDIA GTX 1660 Ti ### What's wrong? I ran the power test on a live Omarchy Quattro desktop: ```bash bash test/shell.d/system-power-test.sh ``` The test passed, but it displayed the real “Rebooting” OSD followed by the real “Shutting down” OSD. The last one remained visible after the test. No real reboot or poweroff occurred. The test safely stubs `systemd-run`, along with `omarchy-state`, `omarchy-hyprland-window-close-all`, and `sleep`. It does not stub `omarchy-osd`. Because the test invokes the real `bin/omarchy-system-reboot` and `bin/omarchy-system-shutdown` scripts, those commands reach the active Omarchy shell and create a real OSD on the developer's desktop. The fix should be pretty simple: add `omarchy-osd` to the test stubs and assert these calls in the existing call log: ```text omarchy-osd -i reboot -m Rebooting -d 5000 omarchy-osd -i shutdown -m Shutting down -d 5000 ``` That preserves the current coverage, verifies the OSD behavior, and keeps the test from changing the active desktop.
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 04:12 UTC