Fix lid close doing nothing on the linux-omarchy kernel
Issue #12873 (open, ASUS Zenbook) supports every claim in symptom and cause: /proc lid state flips, no SW_LID event on event0, EVIOCGRAB succeeds so nothing grabs it, stock 7.2.3-arch1-3 works, and the kernel maintainer's only reply offers a 7.2.7rc1 pre-release for A/B testing. Migration 1789325478.sh read on this workstation: installs linux-omarchy, deletes and re-appends BOOT_ORDER="linux-omarchy, linux-omarchy-*, *, *fallback, Snapshots" in /etc/default/limine, runs sudo limine-mkinitcpio, checks limine-entry-tool --tree, and keeps the old kernel. /usr/lib/limine/limine-common-functions load_config loads /etc/default/limine last as highest priority, so editing BOOT_ORDER there is correct and the drop-in omarchy-defaults.conf BOOT_ORDER is overridden. This machine's /etc/default/limine carries the root and cryptdevice cmdline as the danger says, and the restore value matches what the migration wrote. linux 7.2.3.arch1-3 and linux-omarchy 7.2.5-3 are both installed. Upstream latest is still v4.0.4 and the repo offers linux-omarchy 7.2.5-3, so no fixed kernel has shipped. Not exercised: no lid test, no BOOT_ORDER change, and limine-entry-tool --tree needs root.
Editing /etc/default/limine and rebuilding changes what boots. Keep the other lines in that file untouched, since on Omarchy 4 it carries the root and cryptdevice command line. Check limine-entry-tool --tree lists both kernels before rebooting. Do not remove linux or linux-omarchy while testing.
Symptom
Since the Omarchy 4.0.4 update moved me to the linux-omarchy kernel, closing the lid does nothing: no suspend and no Lid closed. in the journal. /proc/acpi/button/lid/LID/state does change to closed. Booting the old Arch kernel from the Limine menu, lid close suspends normally. Reported on an ASUS Zenbook.
Cause
On linux-omarchy 7.2.5-3 the ACPI button driver updates the lid state in /proc but emits no SW_LID input event on /dev/input/event0, so logind and Hyprland never see the lid close. Nothing is grabbing the device. The same userspace on stock 7.2.3-arch1-3 works. Root cause not confirmed: the kernel maintainer offered a 7.2.7 pre-release for A/B testing, and the issue is open. Omarchy migration 1789325478 installs linux-omarchy, puts it first in BOOT_ORDER, and leaves the previous kernel installed as a fallback.
Fix
**1. Confirm it is the kernel:**
uname -r # ...-omarchy
journalctl -b | grep -E 'Watching system buttons.*Lid|Lid (closed|opened)'
cat /proc/acpi/button/lid/*/state # close the lid partly to see it change
pacman -Q linux linux-omarchy
If the state changes but the journal never logs Lid closed., you have this bug.
**2. Workaround: boot the stock Arch kernel.** At the Limine menu pick the linux entry instead of linux-omarchy. The migration leaves it installed.
**3. To make that the default until a fixed kernel ships,** change BOOT_ORDER in /etc/default/limine, which overrides every drop-in, and rebuild:
grep BOOT_ORDER /etc/default/limine
sudo sed -i 's/^BOOT_ORDER=.*/BOOT_ORDER="linux, linux-omarchy, *, *fallback, Snapshots"/' /etc/default/limine
sudo limine-mkinitcpio
sudo limine-entry-tool --tree
Put it back to BOOT_ORDER="linux-omarchy, linux-omarchy-*, *, *fallback, Snapshots" once an updated linux-omarchy fixes lid events. Report your model on issue #12873 so the kernel maintainer can match it.
Verify
uname -r shows the Arch kernel (-arch1-), and closing the lid logs Lid closed. in journalctl -b -f and suspends.