Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-5218GitHub issuePublicDecided· Out of scope

Screensaver/lock fires during fullscreen YouTube in Firefox-based browsers; shell ignores Hyprland idle_inhibit

Reported by sarniva · filed Oct 7, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 3 days ago.

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

Screensaver/lock fires during fullscreen YouTube in Firefox-based browsers; shell ignores Hyprland idle_inhibitrevision 1 · captured 2026-10-07 20:57 UTC via poll

What happened

Watching a YouTube video fullscreen in Zen Browser (Firefox-based, 1.22.3b), the Omarchy screensaver launches after the idle.screensaver timeout (default 150s) right over the fullscreen video, followed by the lock screen. No input is given because the user is watching.

Chromium does not have this problem: it creates a Wayland idle inhibitor during video playback, which omarchy-shell respects.

Why I think this is an Omarchy bug (not just Zen/Firefox)

Omarchy's own defaults use the Hyprland per-window flag to keep fullscreen apps awake, e.g.:

  • default/hypr/apps/geforce.lua: idle_inhibit = "fullscreen"
  • default/hypr/apps/moonlight.lua, retroarch.lua, steam.lua: same pattern

But the screensaver/lock is now owned by omarchy-shell (shell/plugins/services/idle/Service.qml uses Quickshell IdleMonitor with respectInhibitors: true, driven by shell.json idle.screensaver/idle.lock). I verified that setting the Hyprland window prop (hyprctl clients shows inhibitingIdle: 1 on the Zen window) does not stop the shell screensaver. So the first-party idle_inhibit windowrules cannot suppress the shell screensaver either, and any app that doesn't create its own Wayland inhibitor (all Firefox-based browsers for <video> playback) gets interrupted.

Expected

Fullscreen video playback should inhibit the screensaver/lock regardless of browser, matching Chromium behavior. Options: honor Hyprland fullscreen/inhibitingIdle state in the shell idle service, or ship a fullscreen inhibit rule that the shell actually observes.

Steps to reproduce

  1. Default idle config (shell.json: screensaver: 150, lock: 300), no stay-awake.
  2. Open Zen/Firefox, play any YouTube video, press F for fullscreen.
  3. Don't touch input for 150s.
  4. Screensaver launches over the fullscreen video; lock follows.

System

  • Omarchy: 4.0.4-1 (no omarchy debug subcommand on this build)
  • Hyprland 0.56.2, kernel 7.2.5-3-omarchy
  • CPU: AMD Ryzen 3 5300U with Radeon Graphics; GPU: AMD Lucienne
  • Browser: Mozilla Zen 1.22.3b (also affects Firefox; Chromium unaffected)

Workaround in use

A user helper polling MPRIS + hyprctl -j clients (fullscreen check) that drives the documented stay-awake state (omarchy toggle idle stay-awake/allow-idle). Works, but per-browser polling shouldn't be necessary for fullscreen video.

View raw text
## What happened

Watching a YouTube video fullscreen in Zen Browser (Firefox-based, 1.22.3b), the Omarchy screensaver launches after the `idle.screensaver` timeout (default 150s) right over the fullscreen video, followed by the lock screen. No input is given because the user is watching.

Chromium does not have this problem: it creates a Wayland idle inhibitor during video playback, which omarchy-shell respects.

## Why I think this is an Omarchy bug (not just Zen/Firefox)

Omarchy's own defaults use the Hyprland per-window flag to keep fullscreen apps awake, e.g.:

- `default/hypr/apps/geforce.lua`: `idle_inhibit = "fullscreen"`
- `default/hypr/apps/moonlight.lua`, `retroarch.lua`, `steam.lua`: same pattern

But the screensaver/lock is now owned by omarchy-shell (`shell/plugins/services/idle/Service.qml` uses Quickshell `IdleMonitor` with `respectInhibitors: true`, driven by `shell.json` `idle.screensaver`/`idle.lock`). I verified that setting the Hyprland window prop (`hyprctl clients` shows `inhibitingIdle: 1` on the Zen window) does **not** stop the shell screensaver. So the first-party `idle_inhibit` windowrules cannot suppress the shell screensaver either, and any app that doesn't create its own Wayland inhibitor (all Firefox-based browsers for `<video>` playback) gets interrupted.

## Expected

Fullscreen video playback should inhibit the screensaver/lock regardless of browser, matching Chromium behavior. Options: honor Hyprland fullscreen/`inhibitingIdle` state in the shell idle service, or ship a fullscreen inhibit rule that the shell actually observes.

## Steps to reproduce

1. Default idle config (`shell.json`: `screensaver: 150`, `lock: 300`), no stay-awake.
2. Open Zen/Firefox, play any YouTube video, press F for fullscreen.
3. Don't touch input for 150s.
4. Screensaver launches over the fullscreen video; lock follows.

## System

- Omarchy: 4.0.4-1 (no `omarchy debug` subcommand on this build)
- Hyprland 0.56.2, kernel 7.2.5-3-omarchy
- CPU: AMD Ryzen 3 5300U with Radeon Graphics; GPU: AMD Lucienne
- Browser: Mozilla Zen 1.22.3b (also affects Firefox; Chromium unaffected)

## Workaround in use

A user helper polling MPRIS + `hyprctl -j clients` (fullscreen check) that drives the documented stay-awake state (`omarchy toggle idle stay-awake`/`allow-idle`). Works, but per-browser polling shouldn't be necessary for fullscreen video.

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:22 UTC