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.
Screensaver renders behind pinned (Super + O) windows, leaving the screen visible
Reported by Damndionic · filed Sep 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
System details
AMD Ryzen 7 9800X3D, NVIDIA RTX 4090 (nvidia 610.57.04), Omarchy 4.0.3-1, Hyprland 0.56.2
What's wrong?
The screensaver does not obscure the screen when a window has been popped out with Super + O. The popped-out window stays fully visible and keeps rendering on top of the screensaver for the entire screensaver period.
Plain floating (Super + T) is covered correctly — only the Super + O pop-out is affected.
Steps to reproduce
- Open a terminal (or any app) and press Super + O to pop it out.
- Wait for the idle screensaver, or force it:
omarchy-launch-screensaver force - The screensaver starts, but the popped-out window renders above it.
Expected: the screensaver covers everything on the monitor, the way the lock screen does.
Mechanism
omarchy-hyprland-window-pop floats, resizes, centers, and then pins the window (plus alterzorder top). The screensaver, however, is an ordinary terminal client that only gets window-level rules — default/hypr/apps/system.lua:35-36:
o.window("org.omarchy.screensaver", { fullscreen = true })
o.window("org.omarchy.screensaver", { float = true })Hyprland renders pinned windows in a pass above the workspace's fullscreen window, which is correct pin behavior. So a window-level fullscreen screensaver structurally cannot cover a pinned window. The lock screen isn't affected because it's an overlay layer surface rather than a regular window.
Impact
This happens with stock idle settings (idle.screensaver: 150, idle.lock: 300), so the desktop — and whatever is on screen in the popped-out window — stays visible for 2.5 minutes between screensaver start and lock.
I can attach omarchy-debug output if it's useful, but the repro looks configuration-independent.
<img width="7680" height="2160" alt="Image" src="https://github.com/user-attachments/assets/87ad6d4b-730a-449b-9168-1f670c86737e" />
View raw text
### System details
AMD Ryzen 7 9800X3D, NVIDIA RTX 4090 (nvidia 610.57.04), Omarchy 4.0.3-1, Hyprland 0.56.2
### What's wrong?
The screensaver does not obscure the screen when a window has been popped out with **Super + O**. The popped-out window stays fully visible and keeps rendering on top of the screensaver for the entire screensaver period.
Plain floating (**Super + T**) is covered correctly — only the Super + O pop-out is affected.
**Steps to reproduce**
1. Open a terminal (or any app) and press **Super + O** to pop it out.
2. Wait for the idle screensaver, or force it: `omarchy-launch-screensaver force`
3. The screensaver starts, but the popped-out window renders above it.
**Expected:** the screensaver covers everything on the monitor, the way the lock screen does.
**Mechanism**
`omarchy-hyprland-window-pop` floats, resizes, centers, and then *pins* the window (plus `alterzorder top`). The screensaver, however, is an ordinary terminal client that only gets window-level rules — `default/hypr/apps/system.lua:35-36`:
```lua
o.window("org.omarchy.screensaver", { fullscreen = true })
o.window("org.omarchy.screensaver", { float = true })
```
Hyprland renders pinned windows in a pass above the workspace's fullscreen window, which is correct pin behavior. So a window-level fullscreen screensaver structurally cannot cover a pinned window. The lock screen isn't affected because it's an overlay layer surface rather than a regular window.
**Impact**
This happens with stock idle settings (`idle.screensaver: 150`, `idle.lock: 300`), so the desktop — and whatever is on screen in the popped-out window — stays visible for 2.5 minutes between screensaver start and lock.
I can attach `omarchy-debug` output if it's useful, but the repro looks configuration-independent.
<img width="7680" height="2160" alt="Image" src="https://github.com/user-attachments/assets/87ad6d4b-730a-449b-9168-1f670c86737e" />- 87ad6d4b-730a-449b-9168-1f670c86737e
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 11:22 UTC