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

Stop Left Shift latching into permanent Shift in XWayland apps and games

omarchyhyprlandwaylandxwaylandlaptopdesktop
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

Confirmed on this workstation (omarchy 4.0.4-1, libxkbcommon 1.13.2-1, Hyprland 0.56.2-2): /usr/share/omarchy/default/hypr/input.lua sets kb_options = "compose:caps,shift:both_capslock_cancel", the quattro tree still does, and hyprctl getoption input:kb_options -j returns that string. A read-only xkbcli dump-keymap-x11 against the live XWayland printed modifier_map Shift { <RTSH> }; modifier_map Lock { <LFSH> };. xkbcli compile-keymap --layout us printed Lock { <LFSH> } for the pair, Lock { <CAPS> } for shift:both_capslock_cancel alone, no Lock line for compose:caps alone or compose:caps,grp:alts_toggle, and Lock { <CAPS> } for compose:ralt, so cause, diagnostic and verify hold. Issue #10545 (open) body and comment support the cause, the xkbcli repro, the Proton symptom, the fcitx5 restart and the relaunch gotcha. One defect in the fix: the compose:ralt alternative is offered with no warning. The cited issue itself says it costs Right Alt as Alt/AltGr, which breaks every AltGr layout, and compiling --layout us,ru --options 'compose:ralt,grp:alts_toggle' here shows <RALT> as Multi_key on group 1, so a non-Latin user who combines it with the group switch can no longer leave the us layout. The corrected fix adds both caveats and leaves everything else unchanged. Not exercised: applying the override or reloading Hyprland.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.

Symptom

In X11 (XWayland) apps on Omarchy 4, one tap of Left Shift locks typing into a shifted state: letters come out uppercase and numbers come out as symbols (1 becomes !) until Shift is pressed again. In Proton/XWayland games Shift-bound actions such as sprint just seem dead, which reads as dropped input or lag. Remote-desktop clients send the broken modifier to the remote machine. Wayland-native apps are fine.

Cause

Omarchy 4's packaged /usr/share/omarchy/default/hypr/input.lua sets kb_options = "compose:caps,shift:both_capslock_cancel". Each option is harmless alone, but together they put a Caps_Lock keysym on level 2 of both Shift keys. Wayland clients evaluate the XKB keymap correctly. The legacy core X11 keymap that XWayland exposes derives its modifier map from keysyms, finds Caps_Lock on the Left Shift keycode, assigns that key to Lock and drops it from Shift. xkbcli dump-keymap-x11 shows modifier_map Shift { <RTSH> }; modifier_map Lock { <LFSH> };. Reproduced on this workstation with xkbcli compile-keymap --layout us --options 'compose:caps,shift:both_capslock_cancel', which prints modifier_map Lock { <LFSH> };.

Fix

Confirm the collision (xkbcli ships with libxkbcommon, nothing to install):


xkbcli dump-keymap-x11 | grep -E 'modifier_map (Shift|Lock)'
# broken: modifier_map Shift { <RTSH> };  modifier_map Lock { <LFSH> };
hyprctl getoption input:kb_options

**Omarchy 4:** override the option string in ~/.config/hypr/input.lua. kb_options replaces Omarchy's value and does not merge with it. Keep Caps Lock as Compose and drop the double-Shift Caps Lock chord:


-- ~/.config/hypr/input.lua
hl.config({
  input = {
    kb_options = "compose:caps",
  },
})

**If your layout is non-Latin** (ru, ua, gr, ir, il, ara and the others in Omarchy's list), Omarchy's default prepends us, and adds grp:alts_toggle so you can reach your own layout. Overriding kb_options removes that, so keep a group switch in the new string. Check hyprctl getoption input:kb_options first and copy any grp: option it shows:


hl.config({
  input = {
    kb_options = "compose:caps,grp:alts_toggle",
  },
})

The cost is that Caps Lock cannot be engaged at all. If you need Caps Lock, move Compose instead and keep a plain Caps Lock key:


hl.config({
  input = {
    kb_options = "compose:ralt",
  },
})

compose:ralt turns Right Alt into Compose, so it removes AltGr. Do not use it on a layout that types characters with AltGr (de, pl, no, cz, fr and most other European layouts). Do not combine it with grp:alts_toggle either: both claim Right Alt, and on the us group Right Alt becomes Compose, so the Left Alt + Right Alt switch to your own layout stops working. On those layouts stay with compose:caps.

Apply it, then restart fcitx5 so its virtual keyboard picks up the new keymap:


hyprctl reload
systemctl --user restart omarchy-fcitx5.service

**Relaunch every running XWayland app.** X11 clients read the keyboard map once at startup, so a game or app that was already open keeps the broken map until it is restarted.

**Plain Arch + Hyprland:** the same collision happens with any config that adds a shift:both_capslock* option. Remove it, or swap compose:caps for another compose key, in kb_options in ~/.config/hypr/hyprland.lua.

Verify

xkbcli dump-keymap-x11 | grep -E 'modifier_map (Shift|Lock)' prints modifier_map Shift { <LFSH>, <RTSH> }; with no <LFSH> under Lock. In a freshly launched XWayland app, tapping Left Shift once and typing a1 gives a1.

Sources

xwayland-left-shift-latches-kb-options