No snapshot entries in the Limine menu when you need to roll back
Checked on this Omarchy 4 machine (omarchy-settings 4.0.2-1, limine-snapper-sync 1.31.0-1, limine-mkinitcpio-hook 1.37.1-1) and against the quattro tree and the upstream READMEs. What held: the quoted omarchy-snapshot message is verbatim from /usr/share/omarchy/bin/omarchy-snapshot (identical to quattro), install/config/snapper.sh installs default/snapper/root (NUMBER_LIMIT=5, TIMELINE_CREATE=no) and enables snapper-cleanup.timer plus limine-snapper-sync.service, the service is enabled and running here, limine-snapper-sync/-list/-info/-restore all exist in /usr/bin, the //Snapshots or /Snapshots keyword is documented in the Arch wiki Limine page and the limine-snapper-sync README, MAX_SNAPSHOT_ENTRIES=6 is in /etc/limine-entry-tool.d/omarchy-defaults.conf (owned by omarchy-settings) and PR 6175 shows the value in that drop-in is what limine-snapper-sync reads, ESP_PATH=/boot is in the installer-written /etc/default/limine and in quattro default/limine/default.conf, the probe order /efi, /boot, /boot/efi, /limine is in limine-common-functions, and Direct Boot bypassing the menu is in manual/47-system-snapshots.md and omarchy-setup-direct-boot. Three things were wrong. First, the fix runs sudo omarchy-refresh-limine: the script reads $OMARCHY_PATH, which is exported by default/bash/env-bootstrap and not by any sudoers env_keep (the four files in etc/sudoers.d were read), and sudo's env_reset is on by default, so under sudo the cp "$OMARCHY_PATH/default/limine/limine.conf" step fails after the live config has already been moved to limine.conf.bak. The script is marked requires-sudo and calls sudo itself, so it must be run bare. Second, the cause claims omarchy-refresh-limine can drop the keyword. It does the opposite, because limine-update regenerates the OS entry under BOOT_ORDER="*, *fallback, Snapshots" and the script then runs limine-snapper-sync. Third, /boot is mounted dmask=0077 here (findmnt and fstab), so the unprivileged grep /boot/limine.conf in step 3 prints Permission denied rather than nothing, and LIMIT_USAGE_PERCENT=85 lives in /etc/limine-snapper-sync.conf, which the config grep did not include. Also corrected: with a numeric MAX_SNAPSHOT_ENTRIES the usage limit stops new entries being added, and trimming on usage is the auto behaviour (both from the shipped conf comments). limine-snapper-list was confirmed to work without sudo here. Not exercised: omarchy-refresh-limine itself, a restore, Direct Boot, and the contents of /boot/limine.conf (unreadable without root).
omarchy-refresh-limine overwrites /boot/limine.conf wholesale (old file kept as /boot/limine.conf.bak). limine-update re-adds systemd-boot, rEFInd and the default EFI loader if present (FIND_BOOTLOADERS=yes) but not a Windows entry added with limine-scan, so re-run limine-scan afterwards. Do not prefix it with sudo: sudo drops $OMARCHY_PATH, the template copy fails after the live config has been moved aside, and you boot from a config regenerated without Omarchy's header (no branding, default timeout, default_entry reset). Snapshot restore replaces the root subvolume but not /home and not ~/.config, so a rollback can leave newer config formats in place. Each snapshot entry costs a kernel plus initramfs/UKI on the ESP, and raising MAX_SNAPSHOT_ENTRIES on a small ESP can fill /boot and break the next kernel upgrade. Snapshots created before limine-snapper-sync was installed cannot be made bootable.
Symptom
An update broke the system and the Omarchy manual says to pick a snapshot from the boot loader, but the Limine menu only lists "Omarchy" and maybe a fallback entry. No dated snapshot entries at all. Or the machine boots straight to the disk-decryption prompt and never shows Limine. Sometimes omarchy-snapshot create printed, and you scrolled past:
No Snapper configs found, so no snapshot was created.
Configure Snapper with: sudo bash -euo pipefail "/usr/share/omarchy/install/config/snapper.sh"
Cause
Four independent things must all be true for snapshot entries to appear: snapper must have a root config, limine-snapper-sync.service must be running, /boot/limine.conf must still contain the //Snapshots (or /Snapshots) keyword that tells the tool where to write entries, and the ESP must have room. Any of them silently produces an empty snapshot list. On Omarchy 4 the keyword is placed by limine-entry-tool from BOOT_ORDER="*, *fallback, Snapshots" in /etc/limine-entry-tool.d/omarchy-defaults.conf, so it survives every kernel update. It goes missing when /boot/limine.conf is hand-edited, restored from an old copy, or left empty by a power cut mid-write (FAT32 has no journal). Separately, Omarchy's Setup > Direct Boot adds an EFI entry that jumps past Limine entirely, so the menu is never shown even when the entries exist.
Fix
Work through the four preconditions in order.
**1. Does snapper have a config?**
sudo snapper --csvout list-configs
sudo snapper -c root list
If empty, create it with Omarchy's shipped policy (5 snapshots, no timeline):
sudo bash -euo pipefail /usr/share/omarchy/install/config/snapper.sh
**2. Is the sync service running?**
systemctl status limine-snapper-sync.service
sudo systemctl enable --now limine-snapper-sync.service
**3. Does limine.conf still have the placeholder?** On Omarchy 4 /boot is mounted with dmask=0077, so this needs root or it prints Permission denied instead of the line:
sudo grep -nE '^[[:space:]]*/{1,2}Snapshots' /boot/limine.conf
If that prints nothing on Omarchy 4, regenerate the config. Run this **without** sudo in front: the script calls sudo itself and needs $OMARCHY_PATH, which sudo strips, and with it stripped the script moves your config aside and then fails to copy the template. It keeps the old file as /boot/limine.conf.bak, copies Omarchy's header, then runs limine-update (which rewrites the OS entry and the Snapshots placeholder) and limine-snapper-sync:
omarchy-refresh-limine
On plain Arch, add the keyword by hand inside the OS entry:
/+Arch Linux
//Linux
protocol: linux
path: boot():/vmlinuz-linux
cmdline: root=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx rw rootflags=subvol=/@
module_path: boot():/initramfs-linux.img
//Snapshots
**4. Sync and inspect:**
sudo limine-snapper-sync
limine-snapper-list # works without sudo
sudo limine-snapper-info # shows bootable snapshot count and flags missing/corrupt kernels
Check the caps if fewer snapshots show than exist. With a numeric MAX_SNAPSHOT_ENTRIES (Omarchy ships 6, one above snapper's NUMBER_LIMIT=5 so the freshly created sixth is not reported as an overflow) no entry beyond the cap is written, and once the ESP crosses LIMIT_USAGE_PERCENT (default 85) no new entries are added at all. With MAX_SNAPSHOT_ENTRIES=auto older entries are trimmed instead, without warning. /etc/default/limine overrides everything else:
grep -nE 'ESP_PATH|MAX_SNAPSHOT_ENTRIES|LIMIT_USAGE_PERCENT' /etc/default/limine /etc/limine-entry-tool.d/*.conf /etc/limine-snapper-sync.conf
df -h /boot
If ESP_PATH is unset the tool probes /efi, /boot, /boot/efi, /limine. Omarchy's installer writes ESP_PATH="/boot" into /etc/default/limine.
**Test end to end before you need it:**
omarchy-snapshot create
limine-snapper-list # the new snapshot must appear
**If the menu never appears at all**, Direct Boot is on. Run Setup > Direct Boot from the Omarchy menu again to remove the EFI entry, or press the firmware's boot-device key at power-on and pick Limine manually.
To restore from a snapshot once you can boot one: click the notification that appears inside the snapshot, or run omarchy-snapshot restore / sudo limine-snapper-restore.
Verify
limine-snapper-list shows dated entries, sudo limine-snapper-info reports a non-zero bootable snapshot count with kernels verified, and the entries are visible under "Snapshots" in the Limine menu at the next reboot.
Sources
- https://wiki.archlinux.org/title/Limine
- https://gitlab.com/Zesko/limine-snapper-sync
- https://github.com/basecamp/omarchy/blob/quattro/install/config/snapper.sh
- https://github.com/basecamp/omarchy/blob/quattro/bin/omarchy-snapshot
- https://github.com/basecamp/omarchy/blob/quattro/bin/omarchy-refresh-limine
- https://github.com/basecamp/omarchy/blob/quattro/etc/limine-entry-tool.d/omarchy-defaults.conf
- https://github.com/basecamp/omarchy/blob/quattro/manual/47-system-snapshots.md
- https://wiki.archlinux.org/title/Snapper
- https://gitlab.com/Zesko/limine-snapper-sync/-/blob/master/README.md
- https://github.com/basecamp/omarchy/blob/quattro/bin/omarchy-setup-direct-boot
- https://github.com/basecamp/omarchy/blob/quattro/default/limine/default.conf
- https://github.com/basecamp/omarchy/blob/quattro/default/limine/limine.conf
- https://github.com/basecamp/omarchy/blob/quattro/default/bash/env-bootstrap
- https://github.com/basecamp/omarchy/blob/quattro/manual/50-dual-boot-install.md
- https://github.com/omacom/omarchy/pull/6175
- https://aur.archlinux.org/rpc/v5/info?arg[]=limine-snapper-sync&arg[]=limine-mkinitcpio-hook