OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
power-suspend low common DISPUTE

Get the power button to shut down or suspend again on Omarchy 4

omarchyarchlaptopdesktopsystemdhyprland
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: /etc/systemd/logind.conf.d/10-ignore-power-button.conf (owned by omarchy-settings 4.0.4-1, identical to quattro) sets HandlePowerKey=ignore, busctl reports HandlePowerKey and HandlePowerKeyLongPress both ignore, no handle-power-key inhibitor is held, and systemd-logind has CanReload=yes. logind.conf(5) here gives the 60-90 range for /etc drop-ins and HandlePowerKeyLongPress defaulting to ignore. systemd's logind-button.c on main has LONG_PRESS_DURATION (5 * USEC_PER_SEC), starts the long-press timer only when the long-press action differs from the short one and is not ignore, and logs Power key pressed short. / Power key pressed long., so the fix and verify hold. The defect is in symptom and cause: the binding in /usr/share/omarchy/default/hypr/bindings/utilities.lua is o.bind("XF86PowerOff", "Power menu", "omarchy-menu toggle system", { locked = true }) (quattro uses { menu = "system" } with the same locked = true), so it is meant to fire on a locked session. The symptom's blanket "locked with the screen off, nothing at all" is not supported. Issue #10965 (filed by an AI agent, one human confirmation) describes the hotplug-while-locked input deadlock, where the compositor stops handling input entirely, and that is the case the cause should name. Not exercised: no drop-in written, no button pressed.

The cause above was rewritten on 2026-10-05 to match this note; the fix was corrected by the audit itself.
RISK

HandlePowerKey=poweroff shuts down on a single accidental press, with no prompt and no chance to save work.

Symptom

The power button no longer shuts the machine down or suspends it the way it did on plain Arch, GNOME or KDE. On Omarchy 4 a short press opens the System menu instead. When Hyprland stops handling input, for example after hotplugging a display or dock while the session is locked, pressing it does nothing at all, and the only way out is holding it until the firmware cuts power.

Cause

omarchy-settings ships /etc/systemd/logind.conf.d/10-ignore-power-button.conf with HandlePowerKey=ignore, and Omarchy binds XF86PowerOff to the System menu in /usr/share/omarchy/default/hypr/bindings/utilities.lua with locked = true, so the binding is meant to work on the lock screen too. logind never acts on the key, and the compositor is the only thing that handles it. logind's HandlePowerKeyLongPress= defaults to ignore, so a held press does nothing either until the firmware's own forced power-off. When Hyprland is not handling input at all, as in the hotplug-while-locked deadlock reported in issue #10965, nothing handles the key. Confirmed on this workstation (omarchy-settings 4.0.4-1): busctl reports HandlePowerKey and HandlePowerKeyLongPress both ignore. Plain Arch defaults HandlePowerKey to poweroff.

Fix

Read what logind is enforcing first:


busctl get-property org.freedesktop.login1 /org/freedesktop/login1 \
  org.freedesktop.login1.Manager HandlePowerKey HandlePowerKeyLongPress
systemd-inhibit --list --what=handle-power-key

Omarchy's drop-in is 10-, so a local drop-in has to sort after it. logind.conf(5) suggests the 60 to 90 range for local overrides.

**Omarchy 4, keep the System menu on a short press and add a clean power-off on a long press.** This is also the way out when the compositor is stuck:


sudo install -Dm644 /dev/stdin /etc/systemd/logind.conf.d/90-power-key.conf <<'EOF'
[Login]
HandlePowerKeyLongPress=poweroff
EOF
sudo systemctl reload systemd-logind

logind counts a long press as 5 seconds (LONG_PRESS_DURATION in logind-button.c). Firmware that forces power off at 4 seconds will win that race, so check how your machine behaves.

**Omarchy 4, plain-Arch behaviour on a short press.** Use suspend instead of poweroff if you prefer:


sudo install -Dm644 /dev/stdin /etc/systemd/logind.conf.d/90-power-key.conf <<'EOF'
[Login]
HandlePowerKey=poweroff
EOF
sudo systemctl reload systemd-logind

Hyprland's binding still opens the System menu on the same press, which is harmless because logind acts on the key independently.

Use reload, never restart. Restarting systemd-logind tears down the graphical session, as Omarchy's migration 1784970000.sh notes.

**Plain Arch.** The default is already poweroff. If the button does nothing, the busctl output above shows which value is in force, and the systemd-inhibit line shows whether a desktop component holds a handle-power-key block.

Verify

busctl get-property ... HandlePowerKey HandlePowerKeyLongPress shows the values you set. With journalctl -f -u systemd-logind open in a second terminal, a press logs Power key pressed short. or, with the long-press setting, Power key pressed long. after 5 seconds, followed by the action.

Sources

omarchy-power-button-short-press-ignored