Omarchy 4.0.6 is out, and updates run again after the OpenClaw move
The patch release closes the OpenClaw update block from 4.0.5 and ships four more fixes: a screen that sometimes failed to lock before suspend, a boot passphrase prompt stuck in a non-Latin layout, a console migration tripped up by Limine configs, and TUXEDO drivers that wouldn’t build.
Image: omacom/omarchy release v4.0.6 (GitHub)
Omarchy 4.0.6 is out. Ryan Hughes published it on October 19, 2026, a day after 4.0.5, and the release notes describe it as a patch that “resolves a few small hiccups specific users encountered with v4.0.5.” Existing machines upgrade with Update > Omarchy, and new installs can grab the Omarchy 4.0.6 ISO (SHA256 b542db5fecc37395d9af6654a8146ebed225f275ae4d5a6fcf432e40afe7bb88).
The fix most people were waiting for is the OpenClaw one. As we reported on October 19, 2026, machines with OpenClaw installed could not get past a migration on 4.0.5, which stopped every omarchy update. The release notes list two entries for it: “Fix updates stopping at the OpenClaw migration from 4.0.5” by @spencerbull in #14212, and “Fix the OpenClaw move stopping updates when you have your own OpenClaw” by @emirb in #15875.
There is one manual step for a specific case. According to the release notes, if ~/.local/bin/openclaw is your own npm install, the update leaves it alone and does not move Omarchy’s OpenClaw, and after a reboot the OpenClaw gateway fails to start. To finish the move, the notes say to run: mv ~/.local/bin/openclaw ~/.local/bin/openclaw.mine && systemctl --user reset-failed openclaw-gateway.service && omarchy-install-openclaw-cli --now && systemctl --user start openclaw-gateway.service
Next is a security-flavored fix from DHH himself: the screen sometimes not locking before suspend. In PR #14978, he describes a morning when a suspend left his session unlocked with the message “Screen did not lock before suspend”. The shell’s locked binding read true while the three values behind it were all false, so the lock request assumed the session was already locked and returned without doing anything. He could not reproduce the stalled binding on demand, so the fix makes lock requests read the three real values directly instead of trusting the cached one.
Users with a non-Latin keyboard layout can type their LUKS passphrase again. PR #14885 by @kevincardwell explains that a recent Arch plymouth package started copying /etc/vconsole.conf into the initramfs on its own, bypassing Omarchy’s guard. With a first layout like ru,us or il, Plymouth then asked for the passphrase in that layout, and a Latin passphrase could not be typed. A new mkinitcpio drop-in refuses the file unless you listed it yourself, and a migration rebuilds the boot image once on affected machines.
Another blocked-update case is handled too. PR #15852 by @omarchybot covers machines whose /etc/default/limine sets KERNEL_CMDLINE[default] with a plain =, which replaces everything Omarchy’s drop-ins append to the kernel command line. The console migration could never see its parameter in the rebuilt boot menu, failed, and aborted every update after it. It now recognizes that situation, suggests +=, and finishes.
TUXEDO laptop owners are covered on the packaging side. omarchy-pkgs #1244 by @bastidotnet fixes tuxedo-drivers-nocompatcheck-dkms failing to build on the 7.2.8-9 Omarchy kernel, which carries a patch renaming the ACPI battery hook functions. The DKMS build now maps the old names onto the new ones only when the kernel headers use them, so stock Arch kernels build unchanged.
Ryan Hughes announced the release on X on October 19, 2026 with “Omarchy v4.0.6 has been released!” The full v4.0.5…v4.0.6 changelog is on GitHub. A quick turnaround on a bug that hit a lot of OpenClaw users, and a good reason to run that update today.
Source: https://github.com/omacom/omarchy/releases/tag/v4.0.6
