hyprlock/hypridle break after converting their .conf files to Lua
The diagnosis is right and well sourced. Vaxry's Lua-ification post states other hypr* tools "will for now continue using hyprlang". The hyprlock wiki warns in a box that if no config file is found in any searched path hyprlock "exits with an error and your session will not be locked" (search order $XDG_CONFIG_HOME/hypr/hyprlock.conf, $HOME/.config/hypr/hyprlock.conf, XDG_CONFIG_DIRS, /etc/xdg/hypr/). The hypridle wiki says "A config file is required; hypridle won't run without one" and gives the same autostart / systemctl --user enable --now hypridle.service split. Both hyprlock and hypridle are genuinely in the retired-package removal list inside bin/omarchy-upgrade-to-quattro, so the Omarchy 4 'command not found' framing is accurate. The hyprlang snippets use real options (general:hide_cursor, background monitor/color, input-field size/position/halign/valign/placeholder_text, general lock_cmd/before_sleep_cmd/after_sleep_cmd, listener timeout/on-timeout/on-resume) and hl.dsp.dpms({ action = "on"/"off" }) matches the dispatcher table's documented action values. Two defects in the fix, both copy-paste level. (1) The autostart line is wrong for a daemon: top-level Lua runs on every config load AND every reload/save, so hl.dispatch(hl.dsp.exec_cmd("hypridle")) stacks a new hypridle on each reload. Per the Autostart wiki the once-per-session hook is hl.on("hyprland.start", ...). (2) The 'put the hyprlang versions back' step is mislabeled: mv ~/.config/hypr/hyprlock.lua ~/.config/hypr/hyprlock.conf.bak restores nothing. It only moves the Lua file aside (and .conf.bak is not in hyprlock's search list, which is the one thing it gets right).
A broken hyprlock config is a security failure, not just an annoyance: hypridle's lock_cmd runs, hyprlock exits with a parse error, and the machine goes to sleep or sits idle **unlocked**. Never edit hyprlock.conf and walk away. Run hyprlock from a terminal first and confirm it actually locks. Conversely, if you are already locked out by a crashed lock screen, switch to a TTY with Ctrl+Alt+F2 and pkill hyprlock rather than power-cycling.
Symptom
After migrating hyprland.conf to hyprland.lua for 0.55, the same treatment applied to hyprlock.conf and hypridle.conf kills both. The screen never locks on idle, hypridle exits immediately, running hyprlock by hand prints a config parse error and returns to the shell without locking, or hyprlock starts but the session is left unlocked while the machine sleeps. On Omarchy 4, hyprlock and hypridle are simply not installed and command not found.
Cause
The Lua migration in Hyprland 0.55 applies to **the compositor only**. The rest of the Hypr ecosystem (hyprlock, hypridle, hyprpaper, hyprsunset) still parses hyprlang and still reads .conf files. Renaming or rewriting ~/.config/hypr/hyprlock.conf as Lua leaves hyprlock with nothing it can parse. Upstream is explicit that if no config file is found in any searched path, hyprlock exits with an error and your session will not be locked. hypridle is stricter still: a config file is required and it will not run without one. Separately, Omarchy 4 "Quattro" retired both packages (they appear in the removal list in bin/omarchy-upgrade-to-quattro) in favour of its own Quickshell lock, so an Omarchy 3 config carried forward has nothing left to read it.
Fix
Keep everything as written, with two changes.
(1) Start hypridle from the documented once-per-session hook, not from top-level Lua:
-- ~/.config/hypr/autostart.lua
hl.on("hyprland.start", function()
hl.exec_cmd("hypridle")
end)
On Omarchy the file's own idiom is o.launch_on_start("hypridle"). A bare hl.dispatch(hl.dsp.exec_cmd("hypridle")) at file scope re-executes on every config reload and leaves a pile of daemons. Under uwsm use systemctl --user enable --now hypridle.service instead of either.
(2) Relabel the restore step: moving the Lua file aside is only cleanup, not a restore:
ls -la ~/.config/hypr/ # find hyprlock.lua / hypridle.lua you created
mv ~/.config/hypr/hyprlock.lua ~/.config/hypr/hyprlock.lua.bak # get the unparseable file out of the way
# then either restore your pre-migration hyprlock.conf / hypridle.conf from backup,
# or write the two hyprlang files below from scratch.
On Omarchy 4 the packages are gone, so nothing will read those files until you deliberately sudo pacman -S --needed hyprlock hypridle, which the record correctly advises against unless you mean to replace omarchy-shell's lock.
Verify
hyprlock run from a terminal locks the screen and unlocks with your password (exit code 0, nothing on stderr). hypridle run in the foreground prints no parse errors and locks the session after the configured timeout.
Sources
- https://wiki.hypr.land/Hypr-Ecosystem/hyprlock/
- https://wiki.hypr.land/Hypr-Ecosystem/hypridle/
- https://wiki.hypr.land/Configuring/Start/
- https://github.com/hyprwm/Hyprland/releases/tag/v0.55.0
- https://github.com/basecamp/omarchy/blob/quattro/bin/omarchy-upgrade-to-quattro
- https://wiki.archlinux.org/title/Hyprland