Change Omarchy's screensaver and lock timeouts (and make edits actually take effect)
Checked on this Omarchy 4.0.2-1 workstation (omarchy-settings 4.0.2-1, Hyprland 0.56.2-1). The record's whole mechanism is Omarchy 3 and is false on Omarchy 4. pacman -Q hypridle and pacman -Q hyprlock both report the package is not found, pacman -Qo /usr/bin/hypridle reports no owner, ~/.config/hypr/ contains only Lua files plus hyprsunset.conf and xdph.conf with no hypridle.conf, and gh api repos/omacom/omarchy/git/trees/quattro?recursive=1 returns no path matching hypridle. Idle is instead /usr/share/omarchy/shell/plugins/services/idle/Service.qml, a Quickshell service inside omarchy-shell, reading idle.screensaver and idle.lock from ~/.config/omarchy/shell.json with /usr/share/omarchy/config/omarchy/shell.json as the default, both shipping 150 and 300 seconds. The record's 152 second lock is wrong, the real default is 300. The record's reload instruction is also wrong: there is no hypridle.service, and /usr/share/omarchy/shell/shell.qml gives the user config a FileView with watchChanges: true and onFileChanged: reload(), so an edit applies on save, with omarchy-shell shell reloadConfig as the manual fallback used by omarchy-shell-config. I read the live state read-only with omarchy-shell idle status, which returned "screensaver":150,"lock":300 and confirmed the config path is what the running shell uses. I confirmed the same values in the upstream quattro copies of config/omarchy/shell.json and shell/plugins/services/idle/Service.qml through the GitHub API. I did NOT exercise any timeout, lock the session, or run omarchy-toggle-idle, because Omarchy 4's lock screen cannot be released headlessly. The systemd-inhibit --what=idle advice was dropped because the idle monitor is a Wayland IdleMonitor with respectInhibitors: true and I could not verify that a logind idle inhibitor reaches it, so the fix now names omarchy-toggle-idle stay-awake and Wayland idle inhibitors, which are both in the shipped code. The two basecamp/omarchy master raw URLs still return 200 but master is the Omarchy 3 tree, so they document a file Omarchy 4 does not ship, and the hypridle wiki page describes a daemon that is not installed. All three are removed. This machine is a desktop, so nothing laptop-specific was exercised.
Raising idle.lock leaves the screen unlocked for longer, which matters on a portable machine. omarchy-toggle-idle stay-awake persists across reboot through ~/.local/state/omarchy/indicators/stay-awake, so a machine left in that state never locks itself again until omarchy-toggle-idle allow-idle is run. Hand-writing ~/.config/omarchy/shell.json with only an idle block replaces the shipped defaults entirely, because the shell does not deep merge, and the bar then falls back to a smaller built-in layout.
Symptom
On Omarchy 4 the screensaver appears after 150 seconds of idle and the machine locks at 300 seconds, which is too aggressive while reading or watching something. Editing ~/.config/hypr/hypridle.conf changes nothing, and on a stock Omarchy 4 install that file does not exist.
Cause
Omarchy 4 does not use hypridle. Neither hypridle nor hyprlock is installed, and neither appears anywhere in the upstream quattro tree. Idle, screensaver and lock are a first-party Quickshell service inside omarchy-shell, which reads idle.screensaver and idle.lock from ~/.config/omarchy/shell.json and falls back to /usr/share/omarchy/config/omarchy/shell.json. Both ship 150 seconds for the screensaver and 300 for the lock. Any advice naming ~/.config/hypr/hypridle.conf, lock_cmd, before_sleep_cmd or inhibit_sleep is Omarchy 3 and applies to nothing on Omarchy 4.
Fix
Omarchy 4 has no hypridle and no hyprlock. Neither package is installed (pacman -Q hypridle and pacman -Q hyprlock both report "not found" on 4.0.2-1) and neither exists in the upstream quattro tree. Idle, screensaver and lock are a Quickshell service inside omarchy-shell, at /usr/share/omarchy/shell/plugins/services/idle/Service.qml. The timeouts live in ~/.config/omarchy/shell.json.
Read the live values first:
omarchy-shell idle status | jq
The shipped defaults are 150 seconds to the screensaver and 300 seconds to the lock, from /usr/share/omarchy/config/omarchy/shell.json:
{
"version": 1,
"idle": {
"screensaver": 150,
"lock": 300
}
}
To raise them to five and ten minutes, edit the idle block of your own ~/.config/omarchy/shell.json in place. Edit rather than write a fresh file, because a user shell.json replaces the shipped defaults whole and is not merged into them:
tmp=$(mktemp)
jq '.idle.screensaver = 300 | .idle.lock = 600' ~/.config/omarchy/shell.json > "$tmp" && mv "$tmp" ~/.config/omarchy/shell.json
If ~/.config/omarchy/shell.json does not exist, seed it from the shipped defaults first:
omarchy-refresh-config omarchy/shell.json
The shell watches that file and reloads it on save, so nothing has to be restarted. If a change does not take, force the reload over the shell's own IPC:
omarchy-shell shell reloadConfig
Both values are seconds counted from the moment the session goes idle, not from each other. A lock smaller than screensaver locks without ever showing the screensaver. Anything that is not a non-negative number falls back to the built-in default, silently. The file must keep "version": 1 at the top level or the whole user config is ignored.
To stay awake for one long task instead of changing the config, use the shipped toggle, which is also the Stay Awake entry in the Omarchy menu:
omarchy-toggle-idle stay-awake # no screensaver, no lock, until you turn it back
omarchy-toggle-idle allow-idle # back to normal
omarchy-toggle-idle status
The idle monitor is created with respectInhibitors: true, so an application holding a Wayland idle inhibitor, a full-screen video player for example, already suppresses the idle cycle with no config change at all.
Verify
omarchy-shell idle status | jq '{screensaver, lock, enabled, stayAwake}'
It reports the new screensaver and lock in seconds. enabled: false with stayAwake: true means idle is switched off entirely and no timeout will fire, so clear that first with omarchy-toggle-idle allow-idle before timing anything. Then leave the machine alone past the new screensaver time and confirm the screensaver and the lock arrive when expected.