Update of manjaro-keyring gave errors

I’ve had the same errors, and I’ve applied the same solution, but I’m still getting those same errors when reinstalling manjaro-keyring.

I had the exact same error updating manjaro-keyring this morning in pamac.

I refreshed the keys and then reinstalled manjaro-keyring and got the same error:

(1/1) reinstalling manjaro-keyring                      [#############################] 100%
==> Appending keys from manjaro.gpg...
gpg: public key DB323392796CA067 is 3037 days newer than the signature
gpg: error reading key: No public key
gpg: error reading key: No public key
==> Disabling revoked keys in keyring...
  -> Disabled 2 keys.
==> Updating trust database...
gpg: next trustdb check due at 2022-05-02
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Refreshing PackageKit...

manjaro-keyring update via pamac GUI pops up error messages, yet the update appears to have succeded? “Transaction successfully finished.”

Preparing...
Synchronizing package databases...
Resolving dependencies...
Checking inter-conflicts...
Resolving dependencies...
Checking inter-conflicts...
Download of manjaro-keyring (20220421-1) started
Download of manjaro-keyring (20220421-1) finished
Checking keyring...
Checking integrity...
Loading packages files...
Checking file conflicts...
Checking available disk space...
Upgrading manjaro-keyring (20210910-2 -> 20220421-1)...
==> Appending keys from manjaro.gpg...
gpg: public key DB323392796CA067 is 3037 days newer than the signature
gpg: error reading key: No public key
Error while configuring manjaro-keyring
gpg: error reading key: No public key
Error while configuring manjaro-keyring
==> Disabling revoked keys in keyring...
  -> Disabled 2 keys.
==> Updating trust database...
gpg: next trustdb check due at 2022-05-02
Transaction successfully finished.

I thought I’d try re-installl manjaro-keys just to be certain that “all was well”… and it pops up the errors again…

3 Likes

Yeah! Same here, so I’m not the unique one! The Manjaro Keyring update came in today, not within the usual monthly update. Have a nice day!..

3 Likes

I had an update for Thunderbird today and got the keyring issue:

Vorbereitung...
Synchronisiere Paketdatenbanken...
Warnung: libreoffice-fresh-rpm: ignoring package upgrade (6.4.7-2 => 7.3.0-1)
Warnung: lib32-mesa: Lokale Version (22.0.0-1) ist neuer als multilib (21.3.8-2)
Warnung: manjaro-hello: Lokale Version (0.6.7-2) ist neuer als extra (0.6.6-11)
Warnung: python-pyqt5: Lokale Version (5.15.6-7.1) ist neuer als extra (5.15.6-7)
Abhängigkeiten werden aufgelöst...
Interne Konflikte werden überprüft...
Abhängigkeiten werden aufgelöst...
Interne Konflikte werden überprüft...
Herunterladen von manjaro-keyring (20220421-1) gestartet
Herunterladen von manjaro-keyring (20220421-1) beendet
Überprüfe Schlüsselring...
Integrität wird überprüft...
Paketdateien werden geladen...
Dateikonflikte werden überprüft...
Überprüfe verfügbaren Speicherplatz...
Erneuere manjaro-keyring (20210910-2 -> 20220421-1)...
==> Füge Schlüssel aus manjaro.gpg hinzu...
gpg: error reading key: Kein öffentlicher Schlüssel
Fehler beim Konfigurieren von manjaro-keyring
gpg: error reading key: Kein öffentlicher Schlüssel
Fehler beim Konfigurieren von manjaro-keyring
==> Mache widerrufene Schlüssel im Schlüsselbund unbrauchbar...
  -> Disabled 2 keys.
==> Aktualisiere Trust-Datenbank...
gpg: nächste "Trust-DB"-Pflichtüberprüfung am 2022-05-02
Abhängigkeiten werden aufgelöst...
Interne Konflikte werden überprüft...
Herunterladen von thunderbird-i18n-de (91.8.1-1) gestartet
Herunterladen von thunderbird (91.8.1-0.1) gestartet
Herunterladen von thunderbird-i18n-de (91.8.1-1) beendet
Herunterladen von thunderbird-i18n-en-us (91.8.1-1) gestartet
Herunterladen von thunderbird-i18n-en-us (91.8.1-1) beendet
Herunterladen von thunderbird (91.8.1-0.1) beendet
Überprüfe Schlüsselring...
Integrität wird überprüft...
Paketdateien werden geladen...
Dateikonflikte werden überprüft...
Überprüfe verfügbaren Speicherplatz...
Starte Pre-Transaction-Hooks...
Remove Thunderbird Distribution Settings
Erneuere thunderbird (91.8.0-1 -> 91.8.1-0.1)...
Erneuere thunderbird-i18n-de (91.8.0-1 -> 91.8.1-1)...
Erneuere thunderbird-i18n-en-us (91.8.0-1 -> 91.8.1-1)...
Starte Post-Transaction-Hooks...
Arming ConditionNeedsUpdate...
Updating icon theme caches...
Copy Thunderbird Distribution Settings
Updating the desktop file MIME type cache...
Vorgang erfolgreich abgeschlossen.```

Up to now, I did not anything else. Please advice, in case I should ...
Thank You!

When updating Manjaro today, using pamac:

reinstalling manjaro-keyring [########################################] 100%
==> Appending keys from manjaro.gpg...
gpg: error reading key: No public key
gpg: error reading key: No public key
==> Disabling revoked keys in keyring...
   -> Disabled 2 keys.
==> Updating trust database...
gpg: next trust database check on 2022-05-02

+1

thunderbird keyring is corrupt

1 Like

Same here, the manjaro-keyring update (or was it manjaro-pgp?) was packaged with the Thunderbird update for me too. However when I refresh to find new updates, it says everything is up to date. So I’m assuming it’s all fine for now.

1 Like

I didn’t backup my system with timeshift… should i worried about this update?

Is it safe to restart my PC, after this error?

I just try to update a single package, few KB and got a error in Pamac UI.

Preparing...
Synchronizing package databases...
Warning: lib32-mesa: local (22.0.0-1) is newer than multilib (21.3.8-2)
Warning: manjaro-hello: local (0.6.7-2) is newer than extra (0.6.6-11)
Warning: python-pyqt5: local (5.15.6-7.1) is newer than extra (5.15.6-7)
Resolving dependencies...
Checking inter-conflicts...
Resolving dependencies...
Checking inter-conflicts...
Download of manjaro-keyring (20220421-1) started
Download of manjaro-keyring (20220421-1) finished
Checking keyring...
Checking integrity...
Loading packages files...
Checking file conflicts...
Checking available disk space...
Upgrading manjaro-keyring (20210910-2 -> 20220421-1)...
==> Appending keys from manjaro.gpg...
gpg: error reading key: No public key
Error while configuring manjaro-keyring
gpg: error reading key: No public key
Error while configuring manjaro-keyring
==> Disabling revoked keys in keyring...
  -> Disabled 2 keys.
==> Updating trust database...
gpg: next trustdb check due at 2022-05-02
Transaction successfully finished.

Should i worry, that my system won’t boot after a restart?

1 Like

I encountered the same problem concerning the manjaro-keyring as well. Why do I have to restart at all?

You don’t have to. Just wait for the next update which should fix this.

would be nice if there were news from the manjaro-team if this issue will/is solved. actually the updatemanager still resides on the keyring-update that causes the failures. will it be fixed soon ?

1 Like

Atleast i have no see any issues yet from this update errors.

I too am waiting for a solution. Hopefully we get some news or a fix soon.

same problem here i tried doing
pacman-key --refresh-keys
but it just get stuck mid way

Yay! i got fixed i just reset all key and readd them by using following command

Remove all keys

sudo rm -rf /etc/pacman.d/gnupg

Reinitialize files & folders for keys

sudo pacman-key --init

Repopulate keys

sudo pacman-key --populate archlinux manjaro

Reinstall latest keyrings

sudo pacman -Sy gnupg archlinux-keyring manjaro-keyring

Refresh the signature keys

sudo pacman-key --refresh-keys

Now you can upgrade your packages

sudo pacman -Syu
2 Likes

When I execute sudo pacman-key --refresh-keys I still get a lot of “No data” and “Connection timed out”.

If you can’t download pacman-static inside chroot, you could download it outside and copy it to the mounted location and use it then.
After the update, I would recommend reinstalling all your packages, something really bad happened during the update.

However, if this fails, you probably ran out of disk space or broken RAM or disk during the update and fixing it might take insufferable more time than a new install.

same here. tried the same steps of @shadowsofnoxus yesterday with no success. don’t know but the keyrings are corrupted.

1 Like