OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
boot-kernel high common DISPUTE

An ignored .pacnew for mkinitcpio.conf or the boot loader config breaks the next boot

omarchyarchendeavouroscachyosmanjaroliminegrubsystemd-bootluksdesktoplaptop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

Re-audited on 2026-09-06 after the record was exercised on a real Omarchy 4.0.1 VM (research/validation/, 6/6 assertions pass) and checked again on a 4.0.2 workstation with pacman -Qo, pacman -Qii and pacman -Qkk. The remediation (pacdiff, merge never overwrite, rebuild with limine-mkinitcpio and read the output, keep changes in drop-ins) is confirmed on the machine itself: /usr/local/bin/mkinitcpio is a wrapper from limine-mkinitcpio-hook that warns it does not update Limine entries. Three claims were wrong for Omarchy 4. The symptom quoted a .pacnew for /etc/default/limine, but no package owns that file (pacman -Qo errors), so pacman can never write one for it. The package-owned file is /etc/limine-entry-tool.conf, from limine-mkinitcpio-hook, whose header says to copy it to /etc/default/limine and edit the copy. The cause repeated the same error and named limine-entry-tool as the owner. The danger said overwriting /etc/mkinitcpio.conf with its .pacnew removes the encrypt, plymouth and btrfs-overlayfs hooks. On Omarchy 4 it does not: those hooks are assigned wholesale by /etc/mkinitcpio.conf.d/omarchy_hooks.conf, a backup file of omarchy-settings that mkinitcpio reads after the main file, and the effective HOOKS measured on the VM did not change whatever was done to mkinitcpio.conf. Also, a stock install leaves /etc/mkinitcpio.conf [unmodified], so the .pacnew only appears if you edited it. The file on Omarchy 4 that can both get a .pacnew and carry the hook list is omarchy_hooks.conf itself. Symptom, cause and danger rewritten to name the right files. The fix stands as written.

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

On plain Arch, overwriting /etc/mkinitcpio.conf with the .pacnew removes your encryption, plymouth and btrfs hooks and produces an initramfs that cannot open or find the root device: an unbootable machine. On Omarchy 4 the hook list is assigned by /etc/mkinitcpio.conf.d/omarchy_hooks.conf, which mkinitcpio reads after the main file, so replacing mkinitcpio.conf does not touch the hooks, but overwriting omarchy_hooks.conf with its .pacnew drops any hook you added to it by hand. Merge, rebuild, and confirm the rebuild succeeded before you reboot. Keep a fallback boot entry, an LTS kernel, or a working snapshot available while you do this. Deleting a .pacsave loses the only copy of a config from a package you removed.

Symptom

An upgrade prints, somewhere in a long transcript:


warning: /etc/mkinitcpio.conf installed as /etc/mkinitcpio.conf.pacnew
warning: /etc/mkinitcpio.conf.d/omarchy_hooks.conf installed as /etc/mkinitcpio.conf.d/omarchy_hooks.conf.pacnew
warning: /etc/limine-entry-tool.conf installed as /etc/limine-entry-tool.conf.pacnew

Nothing breaks that day. Weeks later a kernel update rebuilds the initramfs and the machine drops to an emergency shell, or the LUKS prompt never appears, or the root device is not found. The file that is actually read no longer matches what the current package expects: a renamed hook, a changed default, a new required entry. Users also break it the other way round by running mv /etc/mkinitcpio.conf.pacnew /etc/mkinitcpio.conf on plain Arch, or by overwriting omarchy_hooks.conf with its .pacnew on Omarchy, which silently deletes whatever hook they had added by hand. You only see these warnings for files you edited: on a stock Omarchy 4 install all three are [unmodified] and pacman replaces them in place.

Cause

pacman never merges configuration. When a package ships a new version of a file you have edited, it writes .pacnew alongside and leaves yours untouched. The files that decide whether this machine can boot are exactly such files. On plain Arch that is /etc/mkinitcpio.conf (from mkinitcpio). On Omarchy 4 the hook list lives in /etc/mkinitcpio.conf.d/omarchy_hooks.conf (a backup file of omarchy-settings), and the Limine entry template is /etc/limine-entry-tool.conf (from limine-mkinitcpio-hook). /etc/default/limine is the user copy that template tells you to make, is owned by no package, and never gets a .pacnew. Because the damage only surfaces at the next initramfs rebuild, the cause and the symptom can be a month apart.

Fix

Find every outstanding file:


sudo pacman -S --needed pacman-contrib
sudo find /etc -name '*.pacnew' -o -name '*.pacsave'
grep -E '\.pacnew|\.pacsave' /var/log/pacman.log | tail -20

Merge them interactively rather than replacing:


sudo DIFFPROG="nvim -d" pacdiff
# or, with a plain pager first:
sudo pacdiff --output

In pacdiff, v views the diff, m merges, o overwrites with the new file, r removes the .pacnew, s skips. For boot-critical files always m, never blindly o.

**After touching anything under /etc/mkinitcpio.conf*, /etc/default/limine, or /etc/limine-entry-tool.d/, rebuild immediately and read the output. Do not reboot on faith:**


sudo limine-mkinitcpio      # Omarchy 4 / Limine + UKI: rebuilds AND installs the UKI
# plain Arch:
sudo mkinitcpio -P
sudo limine-update          # or: bootctl update / grub-mkconfig -o /boot/grub/grub.cfg

There must be no ERROR: Hook '...' cannot be found, no module not found:, and the run must end with Image generation successful (or Unified kernel image generation successful with no skipping line after it).

**Stop it recurring: never edit the package-owned files.** mkinitcpio reads /etc/mkinitcpio.conf.d/*.conf after the main file and those drop-ins take precedence, so put your changes in a file no package owns:


# /etc/mkinitcpio.conf.d/99-local.conf
MODULES+=(vfat nls_cp437)
FILES+=(/etc/vconsole.conf)

Same idea for kernel parameters on Omarchy:


# /etc/limine-entry-tool.d/99-local.conf
KERNEL_CMDLINE[default]+=" amdgpu.dcdebugmask=0x10"

For reference, Omarchy 4 ships its hooks in the package-owned /etc/mkinitcpio.conf.d/omarchy_hooks.conf:


HOOKS=(base udev plymouth keyboard autodetect microcode modconf kms keymap consolefont block encrypt filesystems fsck btrfs-overlayfs)

Do not copy that line into your own drop-in. A later-sorting drop-in that assigns HOOKS= replaces it wholesale, and you will silently lose whatever Omarchy adds in a future release. Use += on MODULES/FILES, and leave HOOKS to the packaged file.

Verify

sudo find /etc -name '*.pacnew' returns nothing. sudo limine-mkinitcpio (or mkinitcpio -P) completes with no ERROR lines. grep -R HOOKS /etc/mkinitcpio.conf /etc/mkinitcpio.conf.d/ shows encrypt/plymouth/filesystems still present if you use them.

Sources

mkinitcpio-pacnew-unhandled-breaks-next-boot