OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
power-suspend medium common DISPUTE

Find the Chromium window that stops the screen ever locking or blanking

omarchyarchcachyoshyprlandwayland
CORRECTED An auditor found the fix wrong or incomplete and rewrote it. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

Cause and steps 1, 2 and 4 match issue #5092 (open) and Hyprland v0.56.2 IdleInhibitor.cpp. SUPER + CTRL + L runs omarchy-system-lock (utilities.lua:126). The defect is step 3's claim that the chromium-based-browser tag covers Chrome web apps. Hyprland v0.56.2 RegexMatchEngine.cpp uses re2::RE2::FullMatch, so the browser.lua pattern ((google-)?[cC]hrom(e|ium)|[bB]rave-browser|[mM]icrosoft-edge|Vivaldi-stable|helium) tags only those exact classes. Web-app windows (class chrome-<site>__..., launched by omarchy-launch-webapp with --app) are never tagged. That excludes the only case the issue reports working: eds-4d5 matched class = "^chrome.*" for Chrome web apps on 4.0.2. A reader whose inhibitor is a web app would apply the tag rule, see no change, and wrongly remove it. The fix now covers both. The earlier audit note's 'web apps included' was wrong for the same reason. Not exercised: no rule applied, no reload.

The cause above was rewritten on 2026-10-04 to match this note; the fix was corrected by the audit itself.

Symptom

With Chromium, Brave or a Chrome web app open, my laptop never locks or blanks, even overnight, though no video is playing and the window is not fullscreen. omarchy-shell idle status sits at "lastEvent": "idle-monitor: active" for hours. Closing the browser fixes it at once.

Cause

Chromium-family browsers assert the Wayland zwp_idle_inhibit_manager_v1 inhibitor on ordinary pages, including a paused video, and keep it. Hyprland treats any visible surface with a protocol inhibitor as inhibiting idle, and both the Omarchy 4 idle service (IdleMonitor { respectInhibitors: true }) and hypridle on plain Arch respect that, so idle never fires and the lock timeout is never reached. First reported for Chromium 146 on Omarchy 3.4.2 with hypridle, re-tested on Chromium 151 with Omarchy 4.0.0, and reported for Brave on CachyOS with hypridle. A Hyprland idle_inhibit = "none" window rule adds no inhibitor but, according to the Hyprland 0.56.2 source quoted in the issue, cannot cancel one the client set itself. One commenter reports it working for Chrome web-app windows, so treat that rule as unconfirmed.

Fix

**1. Find which window holds the inhibitor:**


hyprctl clients -j | jq -r '.[] | select(.inhibitingIdle==true) | "\(.class) | \(.title)"'

**2. Close or reload that window or tab.** Quitting the browser fully clears the inhibitor. That is the only fix confirmed by every reporter.

**3. Optional, unconfirmed (Omarchy 4):** try telling Hyprland to ignore Chromium-family windows, then check whether step 1 still lists them. Omarchy tags the main browser windows (classes chromium, chrome, google-chrome, brave-browser, microsoft-edge, Vivaldi-stable, helium) with chromium-based-browser in /usr/share/omarchy/default/hypr/apps/browser.lua. Hyprland matches a rule's regex against the whole class, so web-app windows, whose class looks like chrome-<site>__-Default, do not get that tag. Cover both. Add this to ~/.config/hypr/hyprland.lua below the require("default.hypr.omarchy") line:


o.window({ tag = "chromium-based-browser" }, { idle_inhibit = "none" })
o.window({ class = "^chrome-.*" }, { idle_inhibit = "none" })

If step 1 printed a class neither line matches, add one more line matching that class.


hyprctl reload
hyprctl clients -j | jq -r '.[] | select(.inhibitingIdle==true) | .class'

The only report of this working is for Chrome web-app windows. If the browser still shows inhibitingIdle=true, the rule has no effect on your build, so remove it.

**4. Lock by hand when you walk away:** Super+Ctrl+L on Omarchy 4 (omarchy-system-lock), or loginctl lock-session on plain Arch with hypridle.

Verify

After closing the offending window, the command in step 1 prints nothing, and the screensaver appears after idle.screensaver seconds.

Sources

chromium-idle-inhibit-session-never-locks