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

Roll back to a Limine snapshot after an update broke the desktop

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

omarchy-snapshot create and omarchy-snapshot restore are verified real (restore shells out to sudo limine-snapper-restore), and manual/47-system-snapshots.md confirms the whole flow including the click-the-notification step. Three corrections. (1) The 'Applies to' tag lists systemd-boot, which is flatly wrong. The manual states the feature 'is only available on installations using the Limine boot loader ... It's not available if you're on GRUB or systemd-boot.' (2) Snapshots are snapper-managed, not raw btrfs: install/config/snapper.sh installs a root config from default/snapper/root with NUMBER_LIMIT=5 and TIMELINE_CREATE=no. (3) It omits the Direct Boot trap. If Setup > Direct Boot is enabled, the firmware boots Omarchy straight past Limine, so the snapshot entries are unreachable until you pick Limine from the BIOS boot menu. That is exactly the situation where a user needs a rollback and cannot find one.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.
RISK

Snapshot restore only restores the root subvolume. /home is NOT rolled back, so ~/.config keeps its post-update state and can still be mismatched. Snapshots only exist on Limine installs. GRUB and systemd-boot installs have no rollback entries. omarchy reinstall overwrites customised configs.

Symptom

An update left the machine broken, with a black screen, a login loop, or a desktop that won't start, and the user wants to get back to the state from 10 minutes ago. They ask "how do I undo an omarchy update?"

Cause

Omarchy takes a btrfs snapshot before every update and registers it as a bootable Limine entry. Most users don't know the entries are there, or they roll back and are then surprised that their dotfiles didn't change back.

Fix

  1. Reboot. At the **Limine** boot menu, pick the snapshot entry labelled with the date and Omarchy version from *before* the bad update (the version shows in the bottom-left corner).

If you never see a Limine menu, you have *Setup > Direct Boot* enabled. The firmware is jumping straight to Omarchy. Interrupt at power-on and choose **Limine** from your BIOS/UEFI boot menu to reach the snapshot entries.

Snapshots require the Limine bootloader (default since Omarchy 2.0). They do not exist on GRUB or systemd-boot installs.

  1. The system boots read-write into that snapshot. A notification appears. Click it to make the rollback permanent, or run:

omarchy-snapshot restore

To take a snapshot manually before doing something risky:


omarchy-snapshot create

Snapshots are managed by snapper against the root config only, and Omarchy keeps the last 5 with no timeline snapshots. Inspect them with:


sudo snapper -c root list

Remember a restore covers the root subvolume only. /home and ~/.config are untouched (see snapshot-restore-does-not-restore-home).

If the desktop is fine but only Omarchy's own config is mangled, skip the rollback:


omarchy-refresh-hyprland     # overwrites ~/.config/hypr/*.lua with defaults (.bak kept)

or the nuclear option, which reinstalls default packages, forces you back to stable, downgrades anything too new, and resets every config file:


omarchy reinstall

Verify

omarchy --version (or the version shown in the Limine entry you booted) reflects the older release, and the desktop starts normally.

Sources

limine-snapshot-rollback