Roll the whole system back to how it was on a given date
Checked the Arch wiki Arch Linux Archive page (raw wikitext, 2026-09-06), the live archive, pkgs.omarchy.org, the Omarchy manual page manual/47-system-snapshots.md on the quattro branch, and this Omarchy 4 workstation. What held: the wiki still gives exactly Server = https://archive.archlinux.org/repos/YYYY/MM/DD/$repo/os/$arch followed by pacman -Syyuu, with archlinux-keyring and ca-certificates first on signature errors and the warning against mixing archive and live mirrors. https://archive.archlinux.org/repos/2026/09/05/ lists core, extra, multilib and the testing and staging repos, and the record's 2026/07/01 date serves core.db (HTTP 200). What was wrong for Omarchy 4: (1) pacman -Syyuu carries both -S and -u, so /usr/bin/omarchy-update-pacman-guard (read here, hooked by 00-omarchy-update-guard.hook with AbortOnFail) aborts it. It needs sudo env OMARCHY_ALLOW_DIRECT_PACMAN=1, and omarchy update is not a substitute because omarchy-update-system-pkgs runs plain pacman -Syu, which never downgrades. (2) pkgs.omarchy.org has no archive: /archive/, /repos/, /snapshots/, /old/ and /history/ all return 404, the repo db lists one version per package, and only the current and previous package files are served (omarchy-4.0.2-1 and 4.0.1-1 return 200, 4.0.0-1 returns 404). The [omarchy] repo has its own Server = line in /etc/pacman.conf rather than the mirrorlist, so the record's recipe rolls core, extra and multilib back while 30 installed packages here (omarchy, omarchy-settings, omarchy-keyring, limine-snapper-sync, limine-mkinitcpio-hook, yay and others) stay built against current Arch. (3) Omarchy's default mirror stable-mirror.omarchy.org reported lastsync 2026-08-25 while the archive reported 2026-09-06, so an archive date is not the same package set Omarchy served on that date. (4) Snapshot rollback is not conditional on Omarchy 4: the omarchy package depends on limine, limine-snapper-sync and snapper, omarchy-update calls omarchy-snapshot create before every update with NUMBER_LIMIT=5 in /usr/share/omarchy/default/snapper/root, and /etc/limine-entry-tool.d/omarchy-defaults.conf puts a Snapshots entry in the Limine boot order with MAX_SNAPSHOT_ENTRIES=6. The manual says restore is done by booting the snapshot from Limine and then running omarchy-snapshot restore (which is sudo limine-snapper-restore, confirmed in /usr/share/omarchy/bin/omarchy-snapshot), and that it restores root but not /home. The fix now leads with that and keeps the archive recipe as the plain Arch branch. (5) The record cited the master branch copy of omarchy-snapshot, which is the Omarchy 3 script (it sets OMARCHY_PATH to ~/.local/share/omarchy). Not exercised: no rollback or restore was run on this machine, and /.snapshots and /boot are not readable without root. Post-merge correction 2026-09-07 by the corpus lint: the rewritten text said sudo omarchy-snapshot create, but /usr/share/omarchy/bin/omarchy-snapshot calls sudo itself and reads OMARCHY_PATH, which sudo strips, so it is run as the user.
This is the highest-risk operation in this list. Mass-downgrading glibc, systemd, the kernel and the bootloader can leave an unbootable system, and the wiki explicitly warns it is unsafe to mix Archive and live mirrors, because a single download failure falls back to a current package and leaves you with mixed epochs. On Omarchy 4 the [omarchy] repo cannot be rolled back at all: it has no archive, and the recipe leaves its packages built against libraries newer than the ones you restore, so prefer the Snapper snapshot and treat the archive as the last resort. Downgrades do not undo config-file migrations, so /etc may be newer than the binaries, and a snapshot restore leaves /home untouched, so ~/.config and Omarchy's migration markers stay at the newer state. Run omarchy-snapshot create or take a full backup before the archive route, keep a live USB ready, and never leave the Archive mirror configured permanently.
Symptom
"My system is broken after an update from a few weeks ago and I don't know which package did it. I want to go back to how it was on a specific date."
Cause
No single package is identifiable as the culprit, so individual downgrades are impractical. The Arch Linux Archive keeps daily snapshots of the Arch repositories, but not of the [omarchy] repo. Omarchy 4 takes a Snapper snapshot of the root subvolume before every omarchy update and lists the last few as bootable entries in Limine, which rolls back everything at once, including the [omarchy] packages.
Fix
**Omarchy 4: restore the pre-update snapshot.** omarchy update runs omarchy-snapshot create before it upgrades anything, and Limine lists those snapshots under a **Snapshots** entry in the boot menu. This is the rollback that also covers the [omarchy] packages, which the Arch Linux Archive does not hold.
- Reboot into Limine. If the machine boots straight to the decryption screen, pick Limine from the firmware boot menu first (the manual's *Setup > Direct Boot* toggle removes the direct entry again).
- Open **Snapshots** and boot the entry dated before the update that broke things. Snapper keeps the last 5 update snapshots, and Limine shows up to 6.
- Inside the booted snapshot, click the restore notification, or run:
omarchy-snapshot restore # runs sudo limine-snapper-restore
- Reboot into the normal entry and confirm with
pacman -Qi linux | grep Versionandsnapper list.
This restores the root subvolume only. /home, including ~/.config and Omarchy's migration markers in ~/.local/state/omarchy/migrations, is left as it is. If nothing is listed under Snapshots, no snapshot exists to restore, and only the archive recipe below remains.
**Plain Arch, or an Omarchy install with no usable snapshot: the Arch Linux Archive.** Point core, extra and multilib at a dated snapshot by replacing the mirrorlist:
sudo cp /etc/pacman.d/mirrorlist /etc/pacman.d/mirrorlist.bak
sudo tee /etc/pacman.d/mirrorlist >/dev/null <<'EOF'
Server = https://archive.archlinux.org/repos/2026/07/01/$repo/os/$arch
EOF
Then force the downgrade. -uu is what permits downgrades. On Omarchy the update guard aborts any pacman command carrying both -S and -u, so the bypass variable is required, and omarchy update cannot do this because it runs pacman -Syu without the second u:
# plain Arch
sudo pacman -Syyuu
# Omarchy 4
sudo env OMARCHY_ALLOW_DIRECT_PACMAN=1 pacman -Syyuu
If signature errors appear, update the keyring and CA bundle from the archive date first, then immediately run the full downgrade again so nothing is left partially upgraded:
sudo pacman -Sy archlinux-keyring ca-certificates && sudo env OMARCHY_ALLOW_DIRECT_PACMAN=1 pacman -Syyuu
On Omarchy the [omarchy] repo has its own Server = https://pkgs.omarchy.org/stable/$arch line in /etc/pacman.conf and is not affected by the mirrorlist, so omarchy, omarchy-settings, limine-snapper-sync, limine-mkinitcpio-hook, yay and the other packages from it stay at their current versions, built against the Arch libraries you just rolled back. Expect breakage there. Omarchy's stock mirror (stable-mirror.omarchy.org) also lags Arch by days, so an archive date is newer than what Omarchy served on that date.
To return to normal afterwards:
sudo cp /etc/pacman.d/mirrorlist.bak /etc/pacman.d/mirrorlist
# plain Arch
sudo pacman -Syyu
# Omarchy 4
omarchy update
Verify
pacman -Qi linux | grep Version (and other key packages) show versions from the target date. The system boots and the regression is gone.
Sources
- https://wiki.archlinux.org/title/Arch_Linux_Archive
- https://wiki.archlinux.org/title/Downgrading_packages
- https://raw.githubusercontent.com/basecamp/omarchy/master/bin/omarchy-snapshot
- https://archive.archlinux.org/
- https://archive.archlinux.org/repos/2026/09/05/
- https://archive.archlinux.org/repos/2026/07/01/core/os/x86_64/core.db
- https://pkgs.omarchy.org/stable/x86_64/omarchy.db
- https://pkgs.omarchy.org/stable/x86_64/omarchy-4.0.1-1-any.pkg.tar.zst
- https://stable-mirror.omarchy.org/lastsync
- https://github.com/basecamp/omarchy/blob/quattro/manual/47-system-snapshots.md
- https://github.com/basecamp/omarchy/blob/quattro/bin/omarchy-snapshot
- https://github.com/basecamp/omarchy/blob/quattro/install/config/snapper.sh
- https://github.com/basecamp/omarchy/blob/quattro/default/snapper/root