OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
boot-kernel high very-common DISPUTE

Signature errors block every upgrade after months without updating (archlinux-keyring too old)

omarchyarchendeavouroscachyosmanjarodesktoplaptop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

The cause, the clock check, the keyring-first principle, omarchy-update-keyring, the Omarchy key fingerprint 40DFB630FF42BCFFB047046CF0134EE680CAC571 with keys.openpgp.org + --lsign-key + omarchy-keyring (all three verified verbatim in bin/omarchy-update-keyring), the gnupg reset, and the geo.mirror.pkgbuild.com fallback are right. But the explicit reassurance about Omarchy is false and leaves the user in the exact state the record warns against. bin/omarchy-update-pacman-guard sets has_sync on any short option containing S and has_sysupgrade on any containing u, and blocks when both are set, so sudo pacman -Su is blocked just as -Syu is. The recommended sudo pacman -Sy --needed archlinux-keyring && sudo pacman -Su therefore syncs the database and then refuses the upgrade, leaving a partially-synced system.

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

Never stop after pacman -Sy. That leaves the sync database ahead of your installed packages, and the next single-package install becomes a partial upgrade that can break glibc/kernel pairing. Always chain && pacman -Su. Do not "fix" this by setting SigLevel = Never or TrustAll in /etc/pacman.conf: you disable package authentication system-wide. Deleting /etc/pacman.d/gnupg also drops any locally signed third-party keys, which must be re-added afterwards.

Symptom

Any attempt to update fails before installing anything:


error: linux: signature from "Some Maintainer <maintainer@archlinux.org>" is unknown trust
:: File /var/cache/pacman/pkg/linux-7.0.3-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.

On Omarchy this shows up as omarchy update failing in the package step. It blocks every other repair you might want to attempt, because you cannot install anything.

Cause

Package signatures are verified against the keys in /etc/pacman.d/gnupg, which are shipped by the archlinux-keyring package. Maintainers rotate and add keys constantly, so a machine that has not updated for a few months holds a keyring that predates the keys on the current packages. A wrong system clock produces the same class of error (signature ... is invalid) because keys look expired or not-yet-valid.

Fix

Clock first, keyring before everything else, which is unchanged:


timedatectl
sudo timedatectl set-ntp true

On Omarchy 4, use the packaged path (it recv/lsigns the Omarchy key, installs omarchy-keyring, and reinstalls archlinux-keyring even without a version bump):


omarchy-update-keyring
omarchy update

Do not use sudo pacman -Sy --needed archlinux-keyring && sudo pacman -Su on Omarchy. The ALPM guard blocks any pacman run carrying both -S and -u, and that includes a bare -Su: the first half syncs the databases, the second half is refused, and you are left with a synced-but-not-upgraded system, the partial-upgrade state this record exists to avoid. If you must drive pacman directly:


sudo pacman -Sy --needed archlinux-keyring
sudo env OMARCHY_ALLOW_DIRECT_PACMAN=1 pacman -Su

On plain Arch/EndeavourOS/CachyOS (no guard) the original one-liner is correct as written.

The rest of the record stands, with one caveat: sudo rm -rf /etc/pacman.d/gnupg also discards every key you locally signed for the AUR or third-party repos, so on Omarchy re-run omarchy-update-keyring (and re-lsign any custom repo keys) after pacman-key --init && pacman-key --populate archlinux. Note pacman -Sc --noconfirm does work, because -Sc's prompt defaults to yes, unlike -Scc's.

Verify

sudo pacman -Syu proceeds past the signature check and reaches the package list. sudo pacman-key --list-keys | wc -l grows. pacman -Q archlinux-keyring shows a recent version.

Sources

archlinux-keyring-outdated-blocks-every-upgrade