Understand what an Omarchy snapshot rollback does and does not restore
Almost everything matches Omarchy 4's own manual (manual/47-system-snapshots.md) close to verbatim: snapshot on every update, pick the dated entry in Limine with the version shown bottom-left, the 'you are in a bootable snapshot' notification, omarchy-snapshot create / omarchy-snapshot restore (the script exists and restore calls limine-snapper-restore), root restored but /home and ~/.config left alone, Limine-only and default since Omarchy 2.0. omarchy-debug and omarchy-reinstall also exist. The one stale piece is the recovery advice: Omarchy 4 has no 'Update > Config' menu entry that restores a single config to its shipped default. Quattro's equivalents are omarchy-refresh-config <path> (copies one shipped config from $OMARCHY_PATH/config into ~/.config, backing up yours) and the per-component refreshers. omarchy-reinstall-configs is the blunt one and is destructive: it replays all of /etc/skel over $HOME.
Rolling back root while keeping /home can leave newer config formats in ~/.config that the older software cannot read. Expect to reset some configs by hand. Snapshot restore is only available on installs using the Limine boot loader (default since Omarchy 2.0). GRUB and systemd-boot installs have no rollback path, so back up before big updates. Restoring does not roll back your documents, so it is not a data-recovery mechanism.
Symptom
An update broke my system. I booted an older snapshot from the Limine boot menu and ran the restore, but my apps still misbehave. Configs seem to be from the broken version, and I am unsure whether my documents were rolled back too.
Cause
Omarchy takes a btrfs snapshot on every update and exposes them in the Limine boot menu. The restore rolls back the root subvolume only. /home, including ~/.config, is deliberately left untouched so personal files survive, which means config files written in a newer format stay behind and can conflict with the older restored system.
Fix
Snapshot/restore flow is right as written (omarchy-snapshot create before anything risky, then reboot, pick the dated Limine entry, then the notification or omarchy-snapshot restore).
For the configs left behind in ~/.config, use Quattro's refreshers rather than a 'Update > Config' menu entry:
omarchy refresh config hypr/hyprland.lua # one shipped config; backs up yours as *.bak.<epoch>
omarchy refresh hyprland # per-component refreshers: hyprland, shell, limine, sddm, ...
Only if you want everything back to defaults:
omarchy reinstall configs # DESTRUCTIVE: re-copies all of /etc/skel over $HOME
omarchy-debug for diagnostics and omarchy-reinstall for a broken component stay as written. Note the config paths are now Lua (~/.config/hypr/hyprland.lua), not .conf.
Verify
After restore and reboot, the version shown in the Limine entry matches the snapshot you selected, and the previously broken behaviour is gone. sudo btrfs subvolume list / shows the restored root.