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.
[Quattro] Notifications render above the fullscreen screensaver
Reported by ClGratton · filed Sep 1, 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
Omarchy 4.0.1 Quattro, Hyprland 0.56.2, Quickshell 0.3.1, NVIDIA RTX 3080 Ti, and two DisplayPort outputs.
Problem
Notification toasts rendered above the fullscreen animated screensaver, exposing notification contents on a screen intended to conceal the session.
<img width="2432" height="1440" alt="Pending Omarchy Migrations notification rendered over the animated screensaver" src="https://github.com/user-attachments/assets/66881bad-d3aa-4f15-b164-6dba679cd1a9" />
Cause
The terminal screensaver is a normal fullscreen Wayland client. Notification popup windows are WlrLayer.Overlay layer-shell surfaces, so the compositor draws them above normal clients unless the notification service explicitly unmaps them.
Verified solution
PR #9629 hides notification popup surfaces while the enabled idle service reports a live screensaver window and pauses popup lifetime timers while hidden. The idle service is resolved through the plugin registry, including user-cloned implementations.
On the dual-output hardware test, a persistent critical notification was visible before the screensaver, absent over both animations, and restored after dismissal with its remaining lifetime intact. Compositor inspection reported zero omarchy-notifications layer surfaces while both screensaver windows were mapped.
View raw text
### System details Omarchy 4.0.1 Quattro, Hyprland 0.56.2, Quickshell 0.3.1, NVIDIA RTX 3080 Ti, and two DisplayPort outputs. ### Problem Notification toasts rendered above the fullscreen animated screensaver, exposing notification contents on a screen intended to conceal the session. <img width="2432" height="1440" alt="Pending Omarchy Migrations notification rendered over the animated screensaver" src="https://github.com/user-attachments/assets/66881bad-d3aa-4f15-b164-6dba679cd1a9" /> ### Cause The terminal screensaver is a normal fullscreen Wayland client. Notification popup windows are `WlrLayer.Overlay` layer-shell surfaces, so the compositor draws them above normal clients unless the notification service explicitly unmaps them. ### Verified solution PR #9629 hides notification popup surfaces while the enabled idle service reports a live screensaver window and pauses popup lifetime timers while hidden. The idle service is resolved through the plugin registry, including user-cloned implementations. On the dual-output hardware test, a persistent critical notification was visible before the screensaver, absent over both animations, and restored after dismissal with its remaining lifetime intact. Compositor inspection reported zero `omarchy-notifications` layer surfaces while both screensaver windows were mapped.
- 66881bad-d3aa-4f15-b164-6dba679cd1a9
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 02:31 UTC