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.
Unable to complete Omarchy Update Process if Monitor is Disconnected During Process
Reported by lastonboard · filed Sep 8, 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
Dell 9020 Running Omarchy 4.0.3 (Verified post bug)
What's wrong?
Summary
A silly bug I'm sure, but I love this OS so much I wanted to make sure someone knew about it.
I have a 4 port KVM and during a standard update process for Omarchy I changed to a different output. When I came back I couldn't view the update process. Now I'm stuck hoping it completed successfully with no easy way to verify.
I know that my setup is unique for most people, but my concern is that this may happen is somebody closes the lid on an older laptop.
Screenshots and files were collected post-bug.
More detailed steps...
- I started my omarchy update by clicking the update icon at the top
- I entered my password
- In less than a minute got a notification on a different computer so I switched to a different output on my KVM and checked it out.
- I switched back to the KVM output for omarchy
- The update window was gone from all virtual desktops.
- I couldn't tell if the update process had completed successfully or was killed
- I restarted the omarchy update by clicking the update icon at the top
- I'm greeted with a screen similar to the normal one, except this one says "An Omarchy update is already running"
- I've repeated the two preceding steps for the last 15 minutes and nothing has changed. I assume the updater is waiting for me to say that it's ok to reboot. I'm gonna yolo and give it a reboot.
<img width="1217" height="866" alt="Image" src="https://github.com/user-attachments/assets/0f3a443d-5057-422f-99d2-bfa294651d32" />
View raw text
### System details Dell 9020 Running Omarchy 4.0.3 (Verified post bug) ### What's wrong? # Summary A silly bug I'm sure, but I love this OS so much I wanted to make sure someone knew about it. I have a 4 port KVM and during a standard update process for Omarchy I changed to a different output. When I came back I couldn't view the update process. Now I'm stuck hoping it completed successfully with no easy way to verify. I know that my setup is unique for most people, but my concern is that this may happen is somebody closes the lid on an older laptop. Screenshots and files were collected post-bug. ## More detailed steps... - I started my omarchy update by clicking the update icon at the top - I entered my password - In less than a minute got a notification on a different computer so I switched to a different output on my KVM and checked it out. - I switched back to the KVM output for omarchy - The update window was gone from all virtual desktops. - I couldn't tell if the update process had completed successfully or was killed - I restarted the omarchy update by clicking the update icon at the top - I'm greeted with a screen similar to the normal one, except this one says *"An Omarchy update is already running"* - I've repeated the two preceding steps for the last 15 minutes and nothing has changed. I assume the updater is waiting for me to say that it's ok to reboot. I'm gonna yolo and give it a reboot. <img width="1217" height="866" alt="Image" src="https://github.com/user-attachments/assets/0f3a443d-5057-422f-99d2-bfa294651d32" /> [omarchy-debug.log](https://github.com/user-attachments/files/31977474/omarchy-debug.log)
- omarchy-debug.log
- 0f3a443d-5057-422f-99d2-bfa294651d32
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/12094· 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 11:13 UTC