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.
Workspaces switch monitors after unlocking the screen.
Reported by hellojakecross · filed Mar 2, 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?
- 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
System details
AMD Ryzen AI 9 HX 370, Radeon 890m
What's wrong?
Since upgrading to 3.4 (restart completed) when my desktop locks and I come back to it, workspaces are no longer on the same monitor they were before. I know I can move them back with the keyboard shortcut to do so (introduced in 3.3 I think - a great feature!)
If there is some logic behind this switch of monitors (and there's a way to put it back to the previous behaviour of sticking to the montitor they were on) please let me know.
View raw text
### System details AMD Ryzen AI 9 HX 370, Radeon 890m ### What's wrong? Since upgrading to 3.4 (restart completed) when my desktop locks and I come back to it, workspaces are no longer on the same monitor they were before. I know I can move them back with the keyboard shortcut to do so (introduced in 3.3 I think - a great feature!) If there is some logic behind this switch of monitors (and there's a way to put it back to the previous behaviour of sticking to the montitor they were on) please let me know.
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.
No decision has been recorded yet.