Omarchy 3 → 4 'Quattro' upgrade stops partway and leaves the machine half-v3, half-v4
Cause is verbatim-accurate against upstream bin/omarchy-upgrade-to-quattro (master, 2447 lines): set -euo pipefail (L8), the three-line red banner including "Re-running is safe and resumes the remaining steps." (L372-374), as_root find /var/cache/pacman/pkg -maxdepth 1 -name 'omarchy-*' -delete (L443) with the same-name/same-version/different-bytes comment, the key 40DFB630FF42BCFFB047046CF0134EE680CAC571 + --keyserver keys.openpgp.org + --lsign-key (L452-453), pkgs.omarchy.org channel servers (L319-327), Legacy Limine configs exist (...) but /boot/limine.conf does not. Do not reboot until the bootloader config is repaired. (L490), the exact four legacy paths (L473-476), timestamped .omarchy-upgrade-to-quattro.<suffix>.bak backups, and --yes / --channel stable|rc|edge (L4). default/limine/limine.conf exists in v3.8.0, so the ~/.local/share/omarchy/... path is valid on a 3.8.x box. Two real defects in the fix. (1) Step 3 is unsafe in the exact state the record is about. The shipped default/limine/limine.conf is a branding/timeout template with ZERO boot entries (verified identical on v3.8.0 and quattro: no protocol:, no path:, no //Snapshots). Copying it blows away whatever entries /boot/limine.conf had, and the block then rm -fs all four alternate configs with no check that limine-update actually regenerated bootable entries. On a machine already displaying "do NOT reboot", that can turn a recoverable state into an unbootable one. Upstream itself gates on grep -qE '(^|[[:space:]])root=' /boot/limine.conf (L615). The record omits that gate. (2) The comment --channel stable / "stay on your current channel explicitly" is wrong: the script auto-detects the channel from the v3 mirrorlist (L58-64, matching stable-mirror.omarchy.org / rc-mirror.omarchy.org / mirror.omarchy.org) and --channel *overrides* that detection (usage L22: "Override the default stable Omarchy package channel"). sudo limine-snapper-sync is fine: ArchWiki's Limine page documents running it by hand as a check step.
This upgrade is one-way. The script's own banner says "Upgrading Omarchy to Quattro is a one-way street! You cannot downgrade from Quattro." Take a snapshot (omarchy-snapshot create) and back up $HOME before starting. A snapshot restore recovers / but never /home. Rebooting while the "Upgrade incomplete" banner is showing can bring the machine up with no network and no desktop, because the pacman repos are already v4 while the installed packages are not. If the Limine config error appeared, do not reboot until /boot/limine.conf exists and limine-update succeeded, or the machine will not boot at all.
Symptom
Running the Omarchy menu (Super + Alt + Space) > Update > "Omarchy To Quattro", or omarchy-upgrade-to-quattro directly, on an Omarchy 3.8.x box stops partway and prints in red:
Upgrade incomplete - do NOT reboot.
The system is part Omarchy 3 and part Omarchy quattro; rebooting now can leave it without a working network or desktop.
Fix the error reported above and run this script again. Re-running is safe and resumes the remaining steps.
The error just above it is usually one of: pacman rejecting cached omarchy-* packages as "invalid or corrupted package (PGP signature)" / checksum failures, error: omarchy-keyring: signature from "Omarchy ..." is unknown trust, or
Error: Legacy Limine configs exist (/boot/limine/limine.conf) but /boot/limine.conf does not. Do not reboot until the bootloader config is repaired.
Cause
omarchy-upgrade-to-quattro is a one-way, multi-stage transaction: it rewrites /etc/pacman.d/mirrorlist and the [omarchy] section of /etc/pacman.conf to point at the Quattro package servers (pkgs.omarchy.org), reinstalls the whole desktop as pacman packages under /usr/share/omarchy, retires a long list of v3 packages, and only then replaces the user's ~/.local/share/omarchy git checkout with a symlink. It runs under set -euo pipefail, so any single failing step aborts and leaves the system with a v4 pacman config and a partly-v3 package set. The most common concrete trigger: pre-Quattro installs have omarchy-* packages cached in /var/cache/pacman/pkg that the Quattro server rebuilt under the same name and version with different bytes, so the cached copies fail the new database's checksum and abort the --noconfirm transaction.
Fix
Do **not** reboot while that banner is on screen. Read the real error above it, clear it, then re-run. The script is idempotent and resumes:
# 1. Cached legacy omarchy-* packages fail the new repo's checksums. This is
# exactly what the script does internally; do it by hand if it aborted early.
sudo find /var/cache/pacman/pkg -maxdepth 1 -name 'omarchy-*' -delete
sudo pacman -Syy
# 2. Keyring / "unknown trust" failures on the [omarchy] repo
sudo pacman -Syy --noconfirm archlinux-keyring omarchy-keyring
# still failing? trust the Omarchy packaging key directly (same key the script uses)
sudo pacman-key --recv-keys 40DFB630FF42BCFFB047046CF0134EE680CAC571 --keyserver keys.openpgp.org
sudo pacman-key --lsign-key 40DFB630FF42BCFFB047046CF0134EE680CAC571
sudo pacman -Syy --noconfirm archlinux-keyring omarchy-keyring
**3. "Legacy Limine configs exist but /boot/limine.conf does not"**: repair the bootloader config BEFORE anything else. Prefer promoting the config you already have: it contains your real kernel entries. The Omarchy default under default/limine/ is only branding + timeout and has **no boot entries at all**, so copying it is a last resort that depends entirely on limine-update regenerating them.
sudo ls -l /boot/limine.conf /boot/limine/limine.conf \
/boot/EFI/limine/limine.conf /boot/EFI/arch-limine/limine.conf \
/boot/EFI/BOOT/limine.conf 2>/dev/null
# 3a. Preferred: promote the alternate that already has working entries
sudo cp -a /boot/limine/limine.conf /boot/limine.conf # or whichever one exists
# 3b. Only if none of them has entries: start from the Omarchy template
# sudo cp ~/.local/share/omarchy/default/limine/limine.conf /boot/limine.conf
# Regenerate kernel + snapshot entries
sudo limine-update
sudo limine-snapper-sync
# GATE - this is the same check the upgrade script uses (do not skip it).
# No output means /boot/limine.conf has no bootable entry: STOP and fix that
# before deleting anything or rebooting.
sudo grep -nE '(^|[[:space:]])root=' /boot/limine.conf
sudo grep -nc '^ *//' /boot/limine.conf # count of entries
# Only once the gate passes, retire the stale alternates (back them up first)
sudo mkdir -p /root/limine-legacy
for f in /boot/limine/limine.conf /boot/EFI/limine/limine.conf \
/boot/EFI/arch-limine/limine.conf /boot/EFI/BOOT/limine.conf; do
[ -f "$f" ] && sudo cp -a "$f" "/root/limine-legacy/$(echo "${f#/boot/}" | tr / _)"
done
sudo rm -f /boot/limine/limine.conf /boot/EFI/limine/limine.conf \
/boot/EFI/arch-limine/limine.conf /boot/EFI/BOOT/limine.conf
# 4. Resume the upgrade
omarchy-upgrade-to-quattro
# non-interactive: omarchy-upgrade-to-quattro --yes
# The channel is auto-detected from your existing /etc/pacman.d/mirrorlist
# (stable-mirror / rc-mirror / mirror.omarchy.org). Pass --channel only to
# OVERRIDE that detection:
# omarchy-upgrade-to-quattro --channel stable|rc|edge
Everything it replaced is backed up next to the original with a timestamped suffix, so you can diff after the fact:
ls -d /etc/pacman.conf.omarchy-upgrade-to-quattro.*.bak \
/etc/pacman.d/mirrorlist.omarchy-upgrade-to-quattro.*.bak \
~/.local/share/omarchy.omarchy-upgrade-to-quattro.*.bak
find ~/.config -maxdepth 3 -name '*.omarchy-upgrade-to-quattro.*.bak'
Verify
omarchy-version reports 4.x, pacman -Q omarchy returns a version, readlink ~/.local/share/omarchy prints /usr/share/omarchy, and omarchy update runs to completion. Also check ls /usr/share/omarchy/bin | head.
Sources
- https://raw.githubusercontent.com/basecamp/omarchy/master/bin/omarchy-upgrade-to-quattro
- https://raw.githubusercontent.com/basecamp/omarchy/master/bin/omarchy-menu
- https://raw.githubusercontent.com/basecamp/omarchy/quattro/docs/update-process.md
- https://learn.omacom.io/2/the-omarchy-manual/101/system-snapshots