Signature failures for chaotic-aur / CachyOS / Omarchy repos that archlinux-keyring cannot fix
The cause is correct and the key material is verified. Chaotic-AUR's key 3056513887B78AEB matches the upstream installer script (sudo pacman-key --recv-key 3056513887B78AEB --keyserver hkp://keyserver.ubuntu.com:80 / --lsign-key 3056513887B78AEB). CachyOS fingerprint 882DCFE48E2051D48E2562ABF3B607488DB35A47 is confirmed as the DB signing key, along with the expired-subkey story behind the 'signature ... is invalid' variant. The Omarchy block is exactly right: bin/omarchy-update-keyring uses fingerprint 40DFB630FF42BCFFB047046CF0134EE680CAC571 with --keyserver keys.openpgp.org, then lsign, then installs omarchy-keyring, and omarchy-update-keyring is the correct command to run (it invokes sudo internally). The SigLevel claim is right too: Omarchy's default/pacman/pacman-stable.conf carries the global SigLevel = Required DatabaseOptional, and per pacman.conf(5) a repo section's own SigLevel overrides it. Verifying the fingerprint before lsign is the correct and often-omitted safety step.
Two commands are the wrong form and both create partial-upgrade exposure. sudo pacman -Sy cachyos-keyring refreshes the databases and then installs a single package against them, leaving every other installed package at a version older than the synced databases, which is the textbook partial upgrade. And the closing sudo pacman -Syy refreshes databases with no upgrade at all, which leaves the system parked in exactly that state until the user happens to run -Syu. -Syy is also the force-refresh form, needed only after a mirror change, so it re-downloads every database for no reason here. The keyring exception people cite (Omarchy's own script does pacman -Sy) only holds when a full -Syu follows immediately in the same script, which is not what a user copy-pasting these lines will do.
SigLevel = Never or TrustAll on a third-party repo disables signature checking for that repo completely. You are then trusting whatever any mirror serves you, with root install rights. Never set it globally and never as a permanent fix. Do not use pacman-key --refresh-keys as a shotgun: it is slow, frequently fails, and can pull in revoked or superseded key material. Do not rm -rf /etc/pacman.d/gnupg unless you are prepared to re-run pacman-key --init && pacman-key --populate and re-import every third-party key, including on a machine you may not be able to update afterwards.
Symptom
error: chaotic-aur: signature from "<maintainer>" is unknown trust
error: failed to synchronize all databases (invalid or corrupted database (PGP signature))
or on CachyOS:
error: cachyos-core-znver4: signature from "CachyOS <admin@cachyos.org>" is invalid
error: cachyos-extra-znver4: signature from "CachyOS <admin@cachyos.org>" is invalid
Updating archlinux-keyring and running pacman-key --populate archlinux change nothing, because the offending key is not an Arch key.
Cause
Every unofficial repository is signed by its own key, which lives in that project's own keyring package (chaotic-keyring, cachyos-keyring, omarchy-keyring, archlinuxcn-keyring, alhp-keyring), never in archlinux-keyring. Until that key is both **imported** and **locally signed**, pacman under the default SigLevel = Required DatabaseOptional refuses the repo. The same error also appears when a project rotates its key or lets a signing subkey expire (CachyOS's 882DCFE4…8DB35A47 had an encryption subkey expire and shipped a stale cachyos-keyring for over a year) and your installed keyring package predates the rotation.
Fix
Everything is unchanged except the two commands below.
**CachyOS** (the expired/rotated admin key, the is invalid variant): install the keyring as part of a full upgrade, not on its own:
sudo pacman-key --recv-keys 882DCFE48E2051D48E2562ABF3B607488DB35A47 --keyserver keyserver.ubuntu.com
pacman-key --finger 882DCFE48E2051D48E2562ABF3B607488DB35A47 # check against CachyOS's published fingerprint
sudo pacman-key --lsign-key 882DCFE48E2051D48E2562ABF3B607488DB35A47
sudo pacman -Syu cachyos-keyring
**Then refresh and upgrade in one step.** Do not stop at a bare -Sy/-Syy: refreshing databases without upgrading leaves the system in a partial-upgrade state.
sudo pacman -Syu
Only if pacman still reports a stale or corrupt database do you need the force-refresh form, and it must still carry the u:
sudo pacman -Syyu
On Omarchy, run omarchy update instead of either.
Verify
sudo pacman -Syy syncs every database with no signature error. pacman-key --list-keys <KEYID> shows the key present with a local signature. pacman -Sl chaotic-aur | head (or pacman -Sl omarchy | head) lists packages.
Sources
- https://wiki.archlinux.org/title/Pacman/Package_signing
- https://wiki.archlinux.org/title/Unofficial_user_repositories
- https://github.com/SharafatKarim/chaotic-AUR-installer/blob/main/install.bash
- https://github.com/CachyOS/distribution/issues/443
- https://github.com/basecamp/omarchy/blob/quattro/bin/omarchy-update-keyring
- https://github.com/basecamp/omarchy/blob/quattro/default/pacman/pacman-stable.conf