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.
Pinned windows (super+O) render above the screensaver
Reported by FlyingBassHot · filed Oct 9, 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
What's wrong
A window popped out with super+O renders above the screensaver. The screensaver's fullscreen animation plays underneath it, so the popped-out window stays visible and readable over the top of what is meant to be a blanked screen.
Steps to reproduce
- Press
super+Oon any window to pop it out (float + pin). - Trigger the screensaver —
omarchy-launch-screensaver forcefrom the menu, or wait for the 150s idle timeout. - The popped-out window is still on top of the fullscreen screensaver.
Expected
The screensaver covers every window, including pinned ones.
Cause
super+O is bound to omarchy-hyprland-window-pop (default/hypr/bindings/tiling.lua:10), which sets pin on the window. The screensaver is configured as fullscreen = true (default/hypr/apps/system.lua:35). In Hyprland, pin renders above all windows including fullscreen ones, so a pinned window always sits over the screensaver.
Verified with hyprctl: while the screensaver window is up (fullscreen=2, 1920x1080), the popped window is still reported pinned=true.
This is stock behavior on 4.0.4-1 with no user config overrides — both halves live in the packaged defaults, so it affects every install.
Possible fix
The screensaver window is already float = true, so also marking it pin = true may be enough — pinned windows are ordered among themselves by z-order, and the screensaver opens last. Not verified that a pinned fullscreen window reliably outranks another pinned window.
System
Omarchy 4.0.4-1, Linux 7.2.5-3-omarchy, Hyprland 0.56.2, Intel Core i5-4690, Intel iGPU.
Diagnostics: https://logs.omarchy.org/ZIZPYi (expires in 24h)
View raw text
**What's wrong** A window popped out with `super+O` renders *above* the screensaver. The screensaver's fullscreen animation plays underneath it, so the popped-out window stays visible and readable over the top of what is meant to be a blanked screen. **Steps to reproduce** 1. Press `super+O` on any window to pop it out (float + pin). 2. Trigger the screensaver — `omarchy-launch-screensaver force` from the menu, or wait for the 150s idle timeout. 3. The popped-out window is still on top of the fullscreen screensaver. **Expected** The screensaver covers every window, including pinned ones. **Cause** `super+O` is bound to `omarchy-hyprland-window-pop` (`default/hypr/bindings/tiling.lua:10`), which sets `pin` on the window. The screensaver is configured as `fullscreen = true` (`default/hypr/apps/system.lua:35`). In Hyprland, `pin` renders above all windows *including fullscreen ones*, so a pinned window always sits over the screensaver. Verified with `hyprctl`: while the screensaver window is up (`fullscreen=2`, 1920x1080), the popped window is still reported `pinned=true`. This is stock behavior on 4.0.4-1 with no user config overrides — both halves live in the packaged defaults, so it affects every install. **Possible fix** The screensaver window is already `float = true`, so also marking it `pin = true` may be enough — pinned windows are ordered among themselves by z-order, and the screensaver opens last. Not verified that a pinned fullscreen window reliably outranks another pinned window. **System** Omarchy 4.0.4-1, Linux 7.2.5-3-omarchy, Hyprland 0.56.2, Intel Core i5-4690, Intel iGPU. Diagnostics: https://logs.omarchy.org/ZIZPYi (expires in 24h)
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 23:24 UTC