Fix keyboard and touchpad settings ignored after the Hyprland 0.55 Lua switch
Checked on this workstation (omarchy 4.0.2-1, omarchy-settings 4.0.2-1, hyprland 0.56.2-1, kernel 7.1.9) against the Hyprland wiki pages the record cites and against Hyprland's own source at tag v0.56.2. What held: the wiki Start page says almost word for word what the record's cause says, including "Since Hyprland 0.55, hyprlang is deprecated in favor of lua", the config being $XDG_CONFIG_HOME/hypr/hyprland.lua, the yellow warning and the line hl.config({ autogenerated = true }) that clears it, and require with / or . as separators resolved relative to hyprland.lua. I confirmed the autogenerated text and the warning overlay in src/config/lua/DefaultConfig.hpp and CConfigManager::postConfigReload. Every option name in the record's block is real and typed as claimed in the wiki config-options table, the hl.gesture form and both examples match the gestures page (fingers, direction, action, with "fullscreen" a listed action), and I confirmed live that hyprctl getoption input:touchpad:tap_to_click resolves with colon nesting. Three things are wrong. First and worst, the cause claims a hyprlang config is "simply not read" on 0.55 and newer. On 0.56.2 it is shadowed, not rejected: Jeremy::getMainConfigPath searches for hyprland.lua first, falls back to hyprland.conf when no Lua file exists, and only generates the autogenerated example when it finds neither. The .conf parser is still compiled in and hyprctl reload full-reset is documented as switching to or from hyprlang. The fallback is gone on Hyprland main, but main is unreleased and v0.56.2 is the newest tag. Second, the whole autogenerated and yellow-bar half of the symptom cannot happen on Omarchy 4: /usr/share/omarchy/bin/omarchy-upgrade-to-quattro lists hypr/hyprland.lua, hypr/input.lua, hypr/bindings.lua, hypr/looknfeel.lua, hypr/monitors.lua and hypr/autostart.lua in always_copy_config_files and installs the packaged copies, backing up what was there, so a hyprland.lua always exists. Third, the fix sends an Omarchy reader to the wrong file and trips two known traps. On Omarchy 4 personal input overrides belong in ~/.config/hypr/input.lua, which is required after default.hypr.omarchy and ships fully commented out. Its kb_options = "caps:escape" replaces rather than merges, so it silently drops Omarchy 4's compose:caps,shift:both_capslock_cancel, and caps:escape collides with compose:caps. Its clickfinger_behavior = false flips the value Omarchy 4 sets in /usr/share/omarchy/default/hypr/input.lua, and the cited issue is about exactly that option: omacom/omarchy#6935 is a Framework touchpad losing right-click entirely after the 4.0 migration because the option was left unset in Lua, and the reporter states plainly that "the 4.0 migration correctly converted this file to the new Lua format". So the cited issue contradicts the record's framing and supports the corrected one. The require rule is also wrong on Omarchy, where /usr/share/omarchy/default/hypr/bootstrap.lua rewrites package.path to ~/.local/state/?.lua;~/.config/?.lua;$OMARCHY_PATH/?.lua rather than leaving Hyprland's configdir/?.lua default from CConfigManager. tap_to_click and disable_while_typing are already Hyprland defaults (both confirmed in the config-options table) and scroll_factor 0.4 is already Omarchy's value, so three of the example's lines are no-ops the reader will misread as a failed edit. Severity dropped from high to medium: on Omarchy 4 nobody loses a config to this, and the real Omarchy consequence is a handful of touchpad defaults changing, which matches the sibling record keyboard-layout-not-applied-hyprland at medium. Frequency stays very-common. ON DUPLICATION: this is not a duplicate of keyboard-layout-not-applied-hyprland, but the two overlap and should cross-reference. This record uniquely holds the Lua migration itself as the cause (hyprland.conf shadowed, the autogenerated config, the warning overlay), the require and split-file mechanics, the gesture syntax move, and the 0.54-and-older branch. The sibling uniquely holds layout specifics, localectl and /etc/vconsole.conf, switchxkblayout, the omarchy.keyboard-layout bar widget, and resolve_binds_by_sym. What genuinely duplicates is the hl.config input block and the kb_options replacement trap. On filing: this record sits in audio-input while the sibling sits in hyprland-config, and neither is about audio. Both are Hyprland input configuration and belong in one category. That is an operator call, but the split is a filing error, not a distinction. NOT exercised: nothing was written, and no reload, eval, keyword or dispatch was run, because this is the operator's live graphical session. There is no touchpad on this machine, so every touchpad claim comes from the wiki, from Omarchy's packaged input.lua and from InputManager.cpp, not from hardware. The autogenerated-config path and the hyprland.conf fallback were read in source at v0.56.2 and never triggered here.
Moved on 2026-09-13 from audio-input to hyprland-config. Its 2026-09-13 re-audit called the old filing an error rather than a distinction: the record is about Hyprland input configuration and has nothing to do with audio. Its slug and its URL are unchanged, so no published page 404s. The same audit found it is NOT a duplicate of keyboard-layout-not-applied-hyprland, now its sibling in this category: that record holds the layout specifics, while this one holds the Lua migration itself, the require and split-file mechanics, the gesture syntax move and the 0.54-and-older branch. A cross-reference was added to the fix rather than merging them.
A Lua syntax error stops the config loading. Hyprland 0.56 has an emergency mode for the worst case: if a Lua error leaves no keybinds registered it shows an error overlay and binds SUPER+Q to a known terminal, SUPER+R to hyprland-run and SUPER+M to exit, so a broken edit does not usually lock you out. Do not rely on it. Run hyprctl reload then hyprctl configerrors from a running session before you log out, and keep a copy of the file you edited. On Omarchy 4, editing ~/.config/hypr/input.lua takes it out of the stock set, so migration /usr/share/omarchy/migrations/1781485962.sh, which sha-gates the packaged copy, stops replacing it on update. That is what you want, and it also means later Omarchy improvements to that file will not reach you.
Symptom
On plain Hyprland, ~/.config/hypr/hyprland.conf stops being read the moment a ~/.config/hypr/hyprland.lua exists: keyboard layout reverts to US, touchpad natural scrolling and tap-to-click stop applying, and gestures stop working. If you had no config at all, Hyprland writes a fresh hyprland.lua example and shows a yellow warning overlay on every start. On Omarchy 4 you never see the autogenerated config or the yellow bar, because the upgrade installs Omarchy's own hypr/hyprland.lua and hypr/input.lua. What you see on Omarchy 4 is narrower: an option you had left at a .conf default is now unset in Lua and the behaviour it used to give is gone. Touchpad right-click is the common one.
Cause
Since Hyprland 0.55 hyprlang is deprecated in favour of Lua and the config is $XDG_CONFIG_HOME/hypr/hyprland.lua, normally ~/.config/hypr/hyprland.lua. Hyprland 0.56.2, which Omarchy 4 ships, has not removed the old parser. Jeremy::getMainConfigPath looks for hyprland.lua first, falls back to hyprland.conf when no Lua file exists, and generates an example hyprland.lua carrying hl.config({ autogenerated = true }) only when it finds neither. hyprctl reload full-reset is documented as switching the config context to or from hyprlang. So a .conf is not rejected, it is shadowed: once any hyprland.lua is present, every input { ... }, device { ... } and gesture = ... line in the .conf is dead. On Omarchy 4 a hyprland.lua is always present, because omarchy-upgrade-to-quattro lists hypr/hyprland.lua, hypr/input.lua, hypr/bindings.lua, hypr/looknfeel.lua, hypr/monitors.lua and hypr/autostart.lua in always_copy_config_files and installs the packaged copies. Omarchy also rewrites package.path in /usr/share/omarchy/default/hypr/bootstrap.lua to ~/.local/state/?.lua;~/.config/?.lua;$OMARCHY_PATH/?.lua, so a require there resolves from those roots and not from the directory holding hyprland.lua.
Fix
**On Omarchy 4 your input settings go in ~/.config/hypr/input.lua, not hyprland.lua.** ~/.config/hypr/hyprland.lua is Omarchy's packaged entry point. It runs /usr/share/omarchy/default/hypr/bootstrap.lua, then require("default.hypr.omarchy"), then require("hypr.input"), so your file loads after Omarchy's defaults and wins.
~/.config/hypr/input.lua ships as one fully commented-out hl.config block. Uncomment only the lines you want and keep the surrounding structure:
-- ~/.config/hypr/input.lua
hl.config({
input = {
-- kb_options REPLACES the previous string, it does not merge. Omarchy 4 sets
-- "compose:caps,shift:both_capslock_cancel" in
-- /usr/share/omarchy/default/hypr/input.lua, so repeat those unless you mean to
-- drop them. caps:escape and compose:caps both claim Caps Lock, so pick one.
kb_options = "compose:caps,shift:both_capslock_cancel",
repeat_rate = 40,
repeat_delay = 250,
follow_mouse = 1,
touchpad = {
natural_scroll = true, -- Hyprland default false, Omarchy 4 also sets false
clickfinger_behavior = true, -- Omarchy 4 already sets this, see the warning below
scroll_factor = 0.4, -- Omarchy 4 already sets this
disable_while_typing = true, -- already the Hyprland default
tap_to_click = true, -- already the Hyprland default
drag_3fg = 1,
},
},
})
**Do not leave clickfinger_behavior unset on a touchpad.** omacom/omarchy#6935 reports right-click dead after the 4.0 migration, neither two-finger nor lower-right corner, on a config that had the line commented out. Setting it explicitly to true or false restores it. true gives two-finger right-click, false gives lower-right corner.
**On plain Hyprland 0.55 or newer** the same block goes in ~/.config/hypr/hyprland.lua. Split files use Lua's require, resolved relative to the directory holding hyprland.lua, and / or . both work as separators:
require("myconf/input")
require("myconf.binds")
That relative rule does not hold on Omarchy 4. bootstrap.lua rewrites package.path to ~/.local/state/?.lua;~/.config/?.lua;$OMARCHY_PATH/?.lua plus Lua's own, which is why Omarchy's entry point writes require("hypr.input") to reach ~/.config/hypr/input.lua.
**Gestures moved too.** The old gesture = 3, horizontal, workspace line becomes:
hl.gesture({ fingers = 3, direction = "horizontal", action = "workspace" })
hl.gesture({ fingers = 4, direction = "up", action = "fullscreen" })
**If Hyprland wrote the config for you**, you had neither hyprland.lua nor hyprland.conf. Remove the hl.config({ autogenerated = true }) line to clear the yellow warning overlay. This does not happen on Omarchy 4, which always installs its own hyprland.lua.
**Apply and check:**
hyprctl reload
hyprctl configerrors
hyprctl getoption input:kb_layout
hyprctl getoption input:touchpad:tap_to_click
getoption prints a set: line as well as the value. set: true means something in your config set it, set: false means you are reading a built-in default and your edit did not land.
**If you are pinned to Hyprland 0.54 or older**, keep the hyprlang hyprland.conf. The 0.54 wiki pages document that syntax. On 0.56 the old parser is still present and hyprctl reload full-reset switches the context to or from hyprlang, but Omarchy 4 does not support running that way.
For the keyboard-layout specifics this record does not cover, the layout list itself, localectl and /etc/vconsole.conf, switchxkblayout, and Omarchy's omarchy.keyboard-layout bar widget, see keyboard-layout-not-applied-hyprland. The two overlap on the hl.config() input block and on the kb_options replacement trap, and this record is the one that explains the Lua migration behind both.
Verify
hyprctl configerrors prints nothing after hyprctl reload. hyprctl getoption input:kb_layout and hyprctl getoption input:touchpad:tap_to_click return the values you set and report set: true, not set: false. hyprctl getoption input:kb_options still contains Omarchy 4's compose:caps,shift:both_capslock_cancel if you meant to keep it. On a laptop, two-finger right-click, natural scrolling and any gesture you added behave as configured.
Sources
- https://wiki.hypr.land/Configuring/Start/
- https://wiki.hypr.land/Configuring/Basics/Variables/
- https://wiki.hypr.land/Configuring/Advanced-and-Cool/Gestures/
- https://wiki.hypr.land/Configuring/Advanced-and-Cool/Using-hyprctl/
- https://github.com/hyprwm/Hyprland/blob/v0.56.2/src/config/supplementary/jeremy/Jeremy.cpp
- https://github.com/hyprwm/Hyprland/blob/main/src/config/lua/DefaultConfig.hpp
- https://github.com/hyprwm/hyprland-wiki/blob/main/content/configuring/core/config-options.md
- https://github.com/hyprwm/hyprland-wiki/blob/main/content/configuring/core/binds/gestures.md
- https://github.com/hyprwm/hyprland-wiki/blob/main/content/configuring/core/advanced-configuration/using-hyprctl.md
- https://github.com/omacom/omarchy/issues/6935
- https://github.com/omacom/omarchy/blob/quattro/default/hypr/input.lua
- https://github.com/omacom/omarchy/blob/quattro/config/hypr/input.lua
- https://github.com/omacom/omarchy/blob/quattro/bin/omarchy-upgrade-to-quattro