Limine snapshot entries start the stock kernel, and rolling back past 4.0.4 removes linux-omarchy for good
Read /usr/share/omarchy/bin/omarchy-update on 4.0.4-1. It runs omarchy-snapshot create before omarchy-update-system-pkgs and then omarchy-migrate, so the snapshot taken by the update that runs migration 1789325478 has no linux-omarchy. omarchy-migrate keys solely on $HOME/.local/state/omarchy/migrations/<name>.sh. The migration's own early exit keys on /var/lib/omarchy/migrations/1789325478, which is on @ and so goes back with a restore. pacman -Qi omarchy shows no dependency on linux-omarchy, and omarchy-update-system-pkgs only runs pacman -Syu, so nothing reinstalls it. Both per-user marker names (1789325478.sh, 1789444024.sh) exist with that spelling here, and 1789444024 only installs headers, so clearing its marker is harmless. limine-entry-tool --tree accepts a depth argument per --help. The README quote 'with its matching kernel versions' is verbatim. One defect: the cause asserts a workstation-specific observation (three snapshot entries at 12:50 against a 12:55 marker). That is not something a reader can check, it is stale since this machine has updated since, and I could not re-check it without root. It is removed from the cause. The marker times 2026-09-18 12:55 do match. The Arch wiki Limine page is general and kept. Not exercised: no snapshot was restored, and the marker-clearing recovery was not run.
Delete only the two marker files named. Removing the whole migrations directory replays every Omarchy migration since install, some of which rewrite your configuration.
Symptom
After the kernel migration you open the Limine Snapshots submenu to roll back, and the snapshot entries only offer linux, not linux-omarchy. Or you restored a snapshot from before the 4.0.4 update, ran omarchy update afterwards, and linux-omarchy never came back: pacman -Q linux-omarchy says it is not installed and the menu shows only the stock kernel.
Cause
limine-snapper-sync adds each snapshot entry "with its matching kernel versions", meaning the kernels installed inside that snapshot's root, with their files kept under /boot/<machine-id>/limine_history/. omarchy update takes its snapshot (omarchy-snapshot create) before omarchy-update-system-pkgs installs anything, so the snapshot made by the very update that ran migration 1789325478 does not contain linux-omarchy, and neither does any older one. Every snapshot from before the migration boots a stock kernel. Only snapshots taken by later updates contain both kernels.
Restoring a pre-migration snapshot rolls back @, which holds the package database, /etc/default/limine and the machine-wide marker /var/lib/omarchy/migrations/1789325478. It does not roll back @home, which holds the per-user marker ~/.local/state/omarchy/migrations/1789325478.sh. omarchy-migrate decides by the per-user marker, so it never reruns the migration, and the omarchy package does not depend on linux-omarchy, so no update reinstalls it. This follows from reading omarchy-migrate, omarchy-update and the migration on 4.0.4. A real restore was not exercised.
Fix
**See which kernels a snapshot entry carries** before booting it:
limine-snapper-list
sudo limine-entry-tool --tree 4
Entries under a snapshot are named after the kernel packages it contains. A snapshot entry for linux boots that snapshot's root with the stock kernel, which is the right pairing for a snapshot taken before the migration.
**After restoring a pre-4.0.4 snapshot, bring the Omarchy kernel back** by clearing your per-user markers for the two kernel migrations and rerunning the update as your user:
ls ~/.local/state/omarchy/migrations/ | grep -E '1789325478|1789444024'
rm ~/.local/state/omarchy/migrations/1789325478.sh ~/.local/state/omarchy/migrations/1789444024.sh
omarchy update
The migration then installs linux-omarchy and its headers again, rewrites BOOT_ORDER and rebuilds its UKI. If it stops with "The Omarchy kernel has no Limine boot entry", follow that record.
If you restored that snapshot on purpose because linux-omarchy broke your hardware, leave the markers alone. You are already on the stock kernel.
Verify
pacman -Q linux-omarchy shows it installed, sudo limine-entry-tool --tree lists it first, and after a reboot uname -r ends in -omarchy. Snapshots created by the next omarchy update list both kernels.