Stop the screensaver and lock firing over a fullscreen Steam game
Checked on this workstation, which runs omarchy 4.0.2-1 and Hyprland 0.56.2, and against issue 6947 read in full with comments. Confirmed here: /usr/share/omarchy/default/hypr/apps/steam.lua line 1 is exactly the rule the record quotes, /usr/share/omarchy/default/hypr/helpers.lua assigns a string match straight to rules.match.class and calls hl.window_rule, the installed /usr/bin/Hyprland exports only RE2's FullMatchN and no PartialMatchN, and /usr/share/omarchy/default/hypr/apps/terminals.lua carries the comment The class is matched in full, so the full-match premise holds. hyprctl clients -j on this session shows fullscreen as an integer and inhibitingIdle as a real field, so both the symptom JSON and the verify block name fields that exist. idle_inhibit is a recognised rule key in the 0.56.2 binary, which also carries the string idle_inhibit rule has unknown mode "{}", and the Hyprland wiki lists the modes as none, always, focus and fullscreen, so both the record's fullscreen and the reported focus variant are valid. hyprctl reload and hyprctl configerrors are both in hyprctl --help here. The comment the fix anchors to, Add any other personal Hyprland configuration below, is present verbatim in /usr/share/omarchy/config/hypr/hyprland.lua, and o is global by then, which my own config already relies on.
The missing link the record left implicit is now in the cause and it checks out here: /usr/share/omarchy/shell/plugins/services/idle/Service.qml lines 250 to 256 run a Quickshell IdleMonitor with respectInhibitors: true, so a Hyprland inhibitor really does suppress Omarchy's screensaver and lock rather than only a hypridle that is not installed.
Issue 6947 supports the claim. The reporter gives the class, the inhibitingIdle: false reading and the same one-line rule, VillainRU confirms the workaround with inhibitingIdle: true and controller-only play past the timeout, cinco gives the gamescope class with inhibitingIdle: false and confirms the gamescope rule, and etherealheim reports the focus variant without a second confirmation, which is how the record already describes it. Corrected rather than ok for two reasons. The record's version line stops at omarchy 4.0.2-1 and quattro, and tag v4.0.3 of 2026-09-08 is newer and still ships the unfixed rule, which I checked with gh api on both refs. And two pull requests now exist, 9651 and 9667, both open on 2026-09-11, both adding only the steam_app_.* rule and neither covering gamescope. The symptom's user and controller counts were also loose, so they are restated exactly. Not exercised: I did not launch Steam or a game, gamescope is not installed here, and I never reloaded the running config, so every live reading of a steam_app_* or gamescope window comes from the issue thread rather than from this machine.
Symptom
A fullscreen Steam or Proton game played with a controller gets the Omarchy screensaver drawn over it after the idle timeout, and the lock screen follows. Mouse and keyboard activity prevent it, controller input does not. hyprctl clients -j shows the game with inhibitingIdle: false:
{
"class": "steam_app_244210",
"title": "Assetto Corsa",
"fullscreen": 2,
"xwayland": true,
"inhibitingIdle": false
}
Four people report the symptom on issue 6947. Three of them name a controller, a Sony DualSense, a GameSir Cyclone 2 and a Steam Controller, and the fourth only says controller. Three give Omarchy 4.0.0-1 and two of those give Hyprland 0.56.2.
Cause
Omarchy's default Steam rule in default/hypr/apps/steam.lua is:
o.window("steam", { float = true, idle_inhibit = "fullscreen" })
o.window with a string assigns that string to rules.match.class and hands the table to hl.window_rule, which is what /usr/share/omarchy/default/hypr/helpers.lua does, and Hyprland 0.56.2 matches a class against the whole string. The rule therefore covers the Steam client, whose class is steam, and not the games, whose XWayland class is steam_app_<appid>. Games started through gamescope expose the class gamescope and miss the rule the same way. A controller does not reset the compositor idle timer on its own, so with no inhibitor the idle timeout runs during play.
The inhibitor is what Omarchy's idle handling watches. /usr/share/omarchy/shell/plugins/services/idle/Service.qml drives a Quickshell IdleMonitor with respectInhibitors: true, default idle.screensaver 150 seconds and idle.lock 300 seconds, so a Hyprland window inhibitor stops both the screensaver and the lock, and a window without one gets both.
Still the shipped default on quattro, on tag v4.0.3 of 2026-09-08, and on omarchy 4.0.2-1:
grep -n idle_inhibit /usr/share/omarchy/default/hypr/apps/steam.lua
Issue 6947 is open. Two pull requests add o.window("steam_app_.*", { idle_inhibit = "fullscreen" }) to that file, 9651 and 9667, and both were still open on 2026-09-11. Neither covers the gamescope class, so the fix below is wider than either.
Fix
Add rules for the game window classes to the end of ~/.config/hypr/hyprland.lua, below the Add any other personal Hyprland configuration below comment:
-- ~/.config/hypr/hyprland.lua
o.window("steam_app_.*", { idle_inhibit = "fullscreen" })
o.window("gamescope", { idle_inhibit = "fullscreen" })
Reload and check the config parsed:
hyprctl reload
hyprctl configerrors
steam_app_.* covers Proton games. A native Linux game can use its own class, so if one still triggers the screensaver, read its class while it is running and add a rule for it:
hyprctl clients -j | jq '.[] | {class, initialClass, title, fullscreen, inhibitingIdle}'
One reporter used idle_inhibit = "focus" instead for games run borderless-windowed rather than fullscreen. Nobody else confirmed that variant.
Verify
With the game fullscreen, the window now reports the inhibitor, and normal idle locking resumes when the game is closed:
hyprctl clients -j | jq '.[] | select(.class | test("^steam_app_|^gamescope")) | {class, fullscreen, inhibitingIdle}'
Expected "fullscreen": 2 and "inhibitingIdle": true. Two reporters confirmed controller-only play past the idle timeout with neither screensaver nor lock activating.
Sources
- https://github.com/omacom/omarchy/issues/6947
- https://github.com/omacom/omarchy/blob/quattro/default/hypr/apps/steam.lua
- https://github.com/omacom/omarchy/blob/quattro/default/hypr/helpers.lua
- https://github.com/omacom/omarchy/pull/9651
- https://github.com/omacom/omarchy/pull/9667
- https://github.com/omacom/omarchy/blob/v4.0.3/default/hypr/apps/steam.lua
- https://wiki.hypr.land/configuring/core/rules/window-rules/
- https://github.com/hyprwm/hyprland-wiki/blob/main/content/configuring/core/rules/window-rules.md