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 triggers during fullscreen YouTube video in Zen Browser (works fine in Chromium)
Reported by ByronSerrano · filed Aug 17, 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
System details
Lenovo IdeaPad Gaming 3 15ARH05, AMD Ryzen 5 4600H, NVIDIA GeForce GTX 1650 Mobile (hybrid AMD Vega + NVIDIA graphics) Omarchy 4.0.0-1 (stable), Linux 7.1.8-arch1-3, Hyprland 0.56.2. Browser: Zen Browser
What's wrong?
What's wrong?
When watching a YouTube video in fullscreen in Zen Browser, the screensaver still activates after the configured idle timeout, even though a video is actively playing. It seems the idle/screensaver system isn't respecting an inhibit request from the browser during fullscreen video playback.
I tested the same scenario in a Chromium-based browser and did not run into this issue at all — the screensaver correctly stays inhibited during fullscreen video playback there. This points to something specific about how Zen Browser (Firefox-based) requests idle inhibition not being picked up properly.
Steps to reproduce
1. Open Zen Browser
2. Play any YouTube video and switch to fullscreen
3. Let the system sit idle (no keyboard/mouse input) past the configured screensaver timeout
4. The screensaver activates anyway, interrupting playback
5. Repeat the same steps in a Chromium-based browser (e.g. Chrome/Brave) — screensaver correctly stays off
Is anyone else experiencing this?
View raw text
### System details Lenovo IdeaPad Gaming 3 15ARH05, AMD Ryzen 5 4600H, NVIDIA GeForce GTX 1650 Mobile (hybrid AMD Vega + NVIDIA graphics) Omarchy 4.0.0-1 (stable), Linux 7.1.8-arch1-3, Hyprland 0.56.2. Browser: Zen Browser ### What's wrong? What's wrong? When watching a YouTube video in fullscreen in Zen Browser, the screensaver still activates after the configured idle timeout, even though a video is actively playing. It seems the idle/screensaver system isn't respecting an inhibit request from the browser during fullscreen video playback. I tested the same scenario in a Chromium-based browser and did not run into this issue at all — the screensaver correctly stays inhibited during fullscreen video playback there. This points to something specific about how Zen Browser (Firefox-based) requests idle inhibition not being picked up properly. Steps to reproduce 1. Open Zen Browser 2. Play any YouTube video and switch to fullscreen 3. Let the system sit idle (no keyboard/mouse input) past the configured screensaver timeout 4. The screensaver activates anyway, interrupting playback 5. Repeat the same steps in a Chromium-based browser (e.g. Chrome/Brave) — screensaver correctly stays off Is anyone else experiencing this?
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.