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/lock triggers during browser video playback (YouTube etc.) — idle service doesn't honor browser screensaver-inhibit requests
Reported by suhaskashyaps · filed Sep 14, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #6475 (R-1888). GitHub close reason: completed.
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?
- Not yet mapped to any requirement or component.
- 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?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
What happened
The idle service locks the screen and/or launches the screensaver while a browser
tab is actively playing video (e.g. YouTube), even though the browser is the
focused, visible window. This happens whether the video is fullscreen or in a
normal windowed tab.
Why this matters
Screensaver/lock-during-playback is one of the oldest solved problems on Linux
desktops — every major DE has honored it for over a decade. On Omarchy it
regresses that: anyone watching a video with the laptop lid open loses their
session mid-playback, which is disruptive on video calls, tutorials, or just
watching something across a room from the keyboard.
Steps to reproduce
- Set idle timeouts short for testing:
omarchy-toggle-idle allow-idle(make
sure stay-awake is off) and confirm screensaver/lock timeouts via
omarchy-debug-idle (defaults: screensaver 150s, lock 300s).
2. Open a browser (reproduced with Chromium) and play any YouTube video,
windowed, not fullscreen.
3. Don't touch mouse/keyboard — just let the video play.
4. Wait past the screensaver timeout.
Expected
Playback should count as activity/should register a screensaver inhibitor, same
as it does under GNOME, KDE, and most other Wayland/X11 desktops.
Actual
The screensaver launches and the session locks on schedule, as if the browser
weren't there.
Likely mechanism (inferred, not proven with a live trace)
Service.qml's idle monitor sets respects inhibitors: true, which appears to
only cover the native Wayland idle-inhibit-unstable-v1 protocol. The only
inhibit rules Omarchy ships live in default/hypr/apps/*.lua as hardcoded
per-app idle_inhibit = "fullscreen" rules (Moonlight, RetroArch, Steam,
GeForce NOW) — there's no entry for browsers, and nothing appears to bridge theorg.freedesktop.ScreenSaver / org.freedesktop.PowerManagement D-Bus inhibit
interfaces that Chromium and Firefox actually call while a <video> element is
playing. If that reading is right, any app relying on those D-Bus calls instead
of the Wayland protocol is silently ignored.
Workaround, and why it's not a real fix
omarchy-toggle-idle stay-awake (the "Stay Awake" bar toggle) works around it,
but it's a blunt instrument — it disables idle/lock/screensaver system-wide, so
you have to remember to flip it back afterward or the machine never locks. Video
playback should suppress idle only while it's actually playing and visible, the
way inhibitors are supposed to work, not require the user to manually suspend
idle handling for the whole session.
System info
- omarchy version: 4.0.3-1
- Hyprland 0.56.2 (v0.56.2, commit efb5099)
- Browser: Chromium (/usr/bin/chromium)
- omarchy-debug-idle confirms: idle_notify timeout 150000ms, respects
inhibitors: true (native protocol only, per above)
Filed by Claude Sonnet 5 via Claude Code.
View raw text
## What happened The idle service locks the screen and/or launches the screensaver while a browser tab is actively playing video (e.g. YouTube), even though the browser is the focused, visible window. This happens whether the video is fullscreen or in a normal windowed tab. ## Why this matters Screensaver/lock-during-playback is one of the oldest solved problems on Linux desktops — every major DE has honored it for over a decade. On Omarchy it regresses that: anyone watching a video with the laptop lid open loses their session mid-playback, which is disruptive on video calls, tutorials, or just watching something across a room from the keyboard. ## Steps to reproduce 1. Set idle timeouts short for testing: `omarchy-toggle-idle allow-idle` (make sure stay-awake is off) and confirm screensaver/lock timeouts via `omarchy-debug-idle` (defaults: screensaver 150s, lock 300s). 2. Open a browser (reproduced with Chromium) and play any YouTube video, windowed, not fullscreen. 3. Don't touch mouse/keyboard — just let the video play. 4. Wait past the screensaver timeout. ## Expected Playback should count as activity/should register a screensaver inhibitor, same as it does under GNOME, KDE, and most other Wayland/X11 desktops. ## Actual The screensaver launches and the session locks on schedule, as if the browser weren't there. ## Likely mechanism (inferred, not proven with a live trace) `Service.qml`'s idle monitor sets `respects inhibitors: true`, which appears to only cover the native Wayland `idle-inhibit-unstable-v1` protocol. The only inhibit rules Omarchy ships live in `default/hypr/apps/*.lua` as hardcoded per-app `idle_inhibit = "fullscreen"` rules (Moonlight, RetroArch, Steam, GeForce NOW) — there's no entry for browsers, and nothing appears to bridge the `org.freedesktop.ScreenSaver` / `org.freedesktop.PowerManagement` D-Bus inhibit interfaces that Chromium and Firefox actually call while a `<video>` element is playing. If that reading is right, any app relying on those D-Bus calls instead of the Wayland protocol is silently ignored. ## Workaround, and why it's not a real fix `omarchy-toggle-idle stay-awake` (the "Stay Awake" bar toggle) works around it, but it's a blunt instrument — it disables idle/lock/screensaver system-wide, so you have to remember to flip it back afterward or the machine never locks. Video playback should suppress idle only while it's actually playing and visible, the way inhibitors are supposed to work, not require the user to manually suspend idle handling for the whole session. ## System info - omarchy version: 4.0.3-1 - Hyprland 0.56.2 (v0.56.2, commit efb5099) - Browser: Chromium (/usr/bin/chromium) - omarchy-debug-idle confirms: idle_notify timeout 150000ms, respects inhibitors: true (native protocol only, per above) Filed by Claude Sonnet 5 via Claude Code.
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.
No decision has been recorded yet.