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] D-Bus idle inhibits are silently dropped since hypridle was replaced — screensaver fires during video playback (reproduced with Zen browser)
Reported by lcd1232 · filed Aug 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
Intel Core i5-1335U, Intel Iris Xe (Raptor Lake-P), Linux 7.1.5-arch1-2, Omarchy 4.0.0.r1472.g283276b, Hyprland 0.56.1, quickshell-git 0.3.0.r18.g10b439f
What's wrong?
Summary
Nothing owns org.freedesktop.ScreenSaver on the session bus in Quattro, so every idle inhibit sent over D-Bus is silently discarded. The screensaver launches at the configured timeout while video is playing.
Omarchy 3 used hypridle, which registers that bus name and honors Inhibit(). Quattro replaced it with the Quickshell idle service, which uses IdleMonitor { respectInhibitors: true } — and that honors only the Wayland zwp_idle_inhibit_manager_v1 protocol. An application that requests its inhibit over D-Bus rather than the Wayland protocol therefore has it dropped on the floor.
I reproduced this with Zen browser. The application is behaving correctly; nothing is listening.
Steps to reproduce
- Fresh Quattro session.
- Play a YouTube or Twitch video in Zen browser (1.21.10b).
- Do not touch the input devices.
- At
idle.screensaver(150s in myshell.json) the screensaver launches over the playing video. Atidle.lock(300s) the session locks.
View raw text
### System details
Intel Core i5-1335U, Intel Iris Xe (Raptor Lake-P), Linux 7.1.5-arch1-2, Omarchy 4.0.0.r1472.g283276b, Hyprland 0.56.1, quickshell-git 0.3.0.r18.g10b439f
### What's wrong?
## Summary
Nothing owns `org.freedesktop.ScreenSaver` on the session bus in Quattro, so every idle inhibit sent over D-Bus is silently discarded. The screensaver launches at the configured timeout while video is playing.
Omarchy 3 used `hypridle`, which registers that bus name and honors `Inhibit()`. Quattro replaced it with the Quickshell idle service, which uses `IdleMonitor { respectInhibitors: true }` — and that honors only the Wayland `zwp_idle_inhibit_manager_v1` protocol. An application that requests its inhibit over D-Bus rather than the Wayland protocol therefore has it dropped on the floor.
I reproduced this with Zen browser. The application is behaving correctly; nothing is listening.
## Steps to reproduce
1. Fresh Quattro session.
2. Play a YouTube or Twitch video in Zen browser (1.21.10b).
3. Do not touch the input devices.
4. At `idle.screensaver` (150s in my `shell.json`) the screensaver launches over the playing video. At `idle.lock` (300s) the session locks.
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
- Related PRpr/9768· confirmed
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 03:59 UTC