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.
Bar draws over the screensaver since it moved to a special workspace
Reported by ssandys · filed Sep 29, 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
Framework 13, AMD Ryzen AI 9 HX 370 / Radeon 890M, Omarchy 4.0.0.r6687.gb18ab49-1 (omarchy-dev), Hyprland 0.56.2, kernel 7.2.5-4-omarchy, foot as default terminal, external monitor (DP-7)
What's wrong?
Since bf44355a9 (#3284), omarchy-launch-screensaver opens each screensaver on a special workspace (special:screensaver-<monitor>), and now the Omarchy bar is drawn on top of the screensaver. Notification popups also show above it; #9629 already covers those.
Expected: the screensaver covers the whole screen, bar included, as it did when it opened on a regular workspace.
Steps to recreate:
1. omarchy-launch-screensaver force
2. The bar stays visible across the top of the screensaver.
State while the screensaver is up:
- screensaver client: workspace: special:screensaver-DP-7, fullscreen: 2, fullscreenClient: 2, floating: true
- hyprctl workspaces: special:screensaver-DP-7 reports hasfullscreen: true
- hyprctl layers: omarchy-bar stays on layer level 2 (top)
Root cause: Hyprland hides top-layer surfaces behind a fullscreen window on the active regular workspace, but not behind a fullscreen window on a special workspace. The bar is a top-layer surface, so a special-workspace screensaver can't cover it, even though it really is fullscreen.
Possible fixes: hide the bar (and other top-layer shell surfaces) while an org.omarchy.screensaver client is mapped, or put the bar on a layer that Hyprland suppresses for special-workspace fullscreen windows.
View raw text
### System details Framework 13, AMD Ryzen AI 9 HX 370 / Radeon 890M, Omarchy 4.0.0.r6687.gb18ab49-1 (omarchy-dev), Hyprland 0.56.2, kernel 7.2.5-4-omarchy, foot as default terminal, external monitor (DP-7) ### What's wrong? Since bf44355a9 (#3284), `omarchy-launch-screensaver` opens each screensaver on a special workspace (`special:screensaver-<monitor>`), and now the Omarchy bar is drawn on top of the screensaver. Notification popups also show above it; #9629 already covers those. Expected: the screensaver covers the whole screen, bar included, as it did when it opened on a regular workspace. Steps to recreate: 1. `omarchy-launch-screensaver force` 2. The bar stays visible across the top of the screensaver. State while the screensaver is up: - screensaver client: `workspace: special:screensaver-DP-7`, `fullscreen: 2`, `fullscreenClient: 2`, `floating: true` - `hyprctl workspaces`: `special:screensaver-DP-7` reports `hasfullscreen: true` - `hyprctl layers`: `omarchy-bar` stays on layer level 2 (top) Root cause: Hyprland hides top-layer surfaces behind a fullscreen window on the active regular workspace, but not behind a fullscreen window on a special workspace. The bar is a top-layer surface, so a special-workspace screensaver can't cover it, even though it really is fullscreen. Possible fixes: hide the bar (and other top-layer shell surfaces) while an `org.omarchy.screensaver` client is mapped, or put the bar on a layer that Hyprland suppresses for special-workspace fullscreen windows.
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 20:08 UTC