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.
Bug: Layout toggle fails on special workspaces
Reported by LeoPazEs · filed Mar 3, 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
AMD Ryzen 7 5700G (16) @ 4.67 GHz, Omarchy 3.4.1
What's wrong?
When attempting to toggle the layout on an active special workspace, the action fails. This happens because the current layout toggle logic relies on the hyprctl activeworkspace. However, when a special workspace is active on a monitor, hyprctl activeworkspace -j does not report it, causing the toggle command to be used in the workspace in the monitor.
To Reproduce
- Open a special workspace on any monitor.
- Attempt to trigger the layout toggle shortcut/command.
- Observe that the layout does not change in the special workspace but in the workspace that the monitor has.
Expected behavior
The layout toggle should work seamlessly on special workspaces, just as it does on standard workspaces.
Root Cause & Resolution
The issue stems from relying on the workspace ID for identification. By switching the logic to check the workspace name instead of the ID, we can bypass the limitation with hyprctl activeworkspace -j. This approach achieves the same functionality while successfully supporting multiple special workspaces with custom names.
Related PR
A fix for this issue has been implemented and submitted in PR #4880.
View raw text
### System details AMD Ryzen 7 5700G (16) @ 4.67 GHz, Omarchy 3.4.1 ### What's wrong? When attempting to toggle the layout on an active special workspace, the action fails. This happens because the current layout toggle logic relies on the hyprctl activeworkspace. However, when a special workspace is active on a monitor, hyprctl activeworkspace -j does not report it, causing the toggle command to be used in the workspace in the monitor. ## To Reproduce 1. Open a special workspace on any monitor. 2. Attempt to trigger the layout toggle shortcut/command. 3. Observe that the layout does not change in the special workspace but in the workspace that the monitor has. ## Expected behavior The layout toggle should work seamlessly on special workspaces, just as it does on standard workspaces. ## Root Cause & Resolution The issue stems from relying on the workspace ID for identification. By switching the logic to check the workspace name instead of the ID, we can bypass the limitation with hyprctl activeworkspace -j. This approach achieves the same functionality while successfully supporting multiple special workspaces with custom names. ## Related PR A fix for this issue has been implemented and submitted in PR #4880.
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/12269· 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 02:38 UTC