I get the same, everything i’ve tried has failed to fix, and 100’s of errors when using command “sudo pacman-key --refresh-keys”, and some other error about “3068 days out of date from signature”
Anyone from the Manjaro team wish to explain this problem?, and how or will it be fixed??
Having the same issue. Can confirm that “pacman-key --refresh-keys” is not helping
Same issue here but a lot of additional messages (sorry for German language, automated translation here (from DeepL)):
Vorbereitung...
Synchronisiere Paketdatenbanken...
Warnung: manjaro-hello: Lokale Version (0.6.7-2) ist neuer als extra (0.6.6-6)
Abhängigkeiten werden aufgelöst...
Interne Konflikte werden überprüft...
Abhängigkeiten werden aufgelöst...
Interne Konflikte werden überprüft...
Herunterladen von manjaro-keyring (20210807-2) gestartet
Herunterladen von manjaro-keyring (20210807-2) 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 (20210622-1 -> 20210807-2)...
==> Füge Schlüssel aus manjaro.gpg hinzu...
==> Signiere die vertrauenswürdigen Schlüssel im Schlüsselbund lokal...
gpg: "Trust-DB" wird überprüft
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 1EB2638FF56C0C53: no user ID for key signature packet of class 10
gpg: key 1EB2638FF56C0C53: no user ID for key signature packet of class 10
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: Tiefe: 0 gültig: 1 signiert: 27 Vertrauen: 0-, 0q, 0n, 0m, 0f, 1u
gpg: Tiefe: 1 gültig: 27 signiert: 82 Vertrauen: 1-, 0q, 0n, 26m, 0f, 0u
gpg: Tiefe: 2 gültig: 76 signiert: 25 Vertrauen: 76-, 0q, 0n, 0m, 0f, 0u
gpg: nächste "Trust-DB"-Pflichtüberprüfung am 2021-10-12
-> Locally signed 1 keys.
==> Importiere die Vertrauenswerte des Benutzers...
gpg: setting ownertrust to 4
==> Mache widerrufene Schlüssel im Schlüsselbund unbrauchbar...
gpg: "Trust-DB" wird überprüft
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 1EB2638FF56C0C53: no user ID for key signature packet of class 10
gpg: key 1EB2638FF56C0C53: no user ID for key signature packet of class 10
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: Tiefe: 0 gültig: 1 signiert: 27 Vertrauen: 0-, 0q, 0n, 0m, 0f, 1u
gpg: Tiefe: 1 gültig: 27 signiert: 82 Vertrauen: 0-, 0q, 0n, 27m, 0f, 0u
gpg: Tiefe: 2 gültig: 76 signiert: 25 Vertrauen: 76-, 0q, 0n, 0m, 0f, 0u
gpg: nächste "Trust-DB"-Pflichtüberprüfung am 2021-10-12
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
-> Disabled 2 keys.
==> Aktualisiere Trust-Datenbank...
gpg: nächste "Trust-DB"-Pflichtüberprüfung am 2021-10-12
Vorgang erfolgreich abgeschlossen.
Same issue with Pamac. Only one single System Update item was on the list: manjaro-keyring (20210807-2). Additionally I got an UI message box containing “Error while configuring manjaro-keyring” twice. (I can provide a screenshot of the message box, if required.)
Below you find the same log as MaMicha’s but in English.
No other problems so far. I just want to provide you the information as a debugging possibility.
Preparing...
Synchronizing package databases...
Resolving dependencies...
Checking inter-conflicts...
Resolving dependencies...
Checking inter-conflicts...
Download of manjaro-keyring (20210807-2) started
Download of manjaro-keyring (20210807-2) finished
Checking keyring...
Checking integrity...
Loading packages files...
Checking file conflicts...
Checking available disk space...
Upgrading manjaro-keyring (20210622-1 -> 20210807-2)...
==> Appending keys from manjaro.gpg...
==> Locally signing trusted keys in keyring...
gpg: checking the trustdb
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 1EB2638FF56C0C53: no user ID for key signature packet of class 10
gpg: key 1EB2638FF56C0C53: no user ID for key signature packet of class 10
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 27 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 27 signed: 82 trust: 1-, 0q, 0n, 26m, 0f, 0u
gpg: depth: 2 valid: 76 signed: 25 trust: 76-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2021-10-12
-> Locally signed 1 keys.
==> Importing owner trust values...
gpg: setting ownertrust to 4
==> Disabling revoked keys in keyring...
gpg: checking the trustdb
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 1EB2638FF56C0C53: no user ID for key signature packet of class 10
gpg: key 1EB2638FF56C0C53: no user ID for key signature packet of class 10
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 27 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 27 signed: 82 trust: 0-, 0q, 0n, 27m, 0f, 0u
gpg: depth: 2 valid: 76 signed: 25 trust: 76-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2021-10-12
gpg: error reading key: No public key
Error while configuring manjaro-keyring
gpg: error reading key: No public key
Error while configuring manjaro-keyring
-> Disabled 2 keys.
==> Updating trust database...
gpg: next trustdb check due at 2021-10-12
Transaction successfully finished.
i have same “error” : “Disabled 2 keys” ( not a problem if this keys are not useful… )
i have no problem for install some packages after this update (packager:helmut,Philip,Bernhard it’s ok) 
to have “no user ID for key signature” is not a problem , I have also some in pacman logs with archlinux-keyring package or here same issue than here
Just received an update for manjaro-keyring and getting the same isses as @lbernd
gpg: error reading key: No public key
Error while configuring manjaro-keyring
gpg: error reading key: No public key
Error while configuring manjaro-keyring
etc.
Gonna leave it for now I suppose.
Thread cleaned. 
Power-posting is best described as posting empty and worthless messages. It is not tolerated. People may have two reasons to do this: to increase their post count meaninglessly, or to lend support to an idea as if it were a vote. Examples of power-posting include, but are not limited to, replying with “+1”, “lol”, “me too”, “I agree”, or “:)”.
When posting or replying to messages, make sure you have something to say. These empty posts clutter up threads and discussion, invalidate the ‘Unread’ and ‘Replies’ functions, and waste bandwidth and server space.
Threads that degenerate into a series of “+1/-1” or “me too/I agree/I disagree” will be locked. Individual power posts may also be deleted. If you believe a topic deserves determination of consensus, please add a poll to it, to satisfy the impulse of others to make empty posts.
Same issue here:
gpg: nächste "Trust-DB"-Pflichtüberprüfung am 2021-10-12
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
-> Disabled 2 keys.Is there a solution @oberon ?
i have this “error” : “Disabled 2 keys” but all is working so no further action for me. 
I got this as well, and running sudo pacman-key --refresh-keys afterwards produced a very long output with lots of errors in it, that went on for some time. I’m new to this so perhaps this is actually nothing special, I can’t really tell. Just hope it doesn’t mess things up iN sUbTlE wAyS and whatnot in the long run if you know what I’m saying.
Same here too, and after reading the rest of comments, will wait for a better solution before trying what’s said so far…
this did it for me:
sudo rm -r /etc/pacman.d/gnupg
sudo pacman-key --init
sudo pacman-key --populate manjaro
sudo pacman-key --populate archlinux
sudo pacman -Syvv manjaro-keyring # for testing, if everything is okay there will be no errors
I have that bug. Olli is the # included? I’m also getting a strange http server redirect during the process.
no, just use. you are aware to use the other commands in this given order first ?
sudo pacman -Syvv manjaro-keyring
I simply don’t get why people try to fix something which is not broken. The thing is:
What we did so far from our end:
All the signatures from that Maintainer got replaced by a generic one from our build-server. This means the GPG key of that maintainer normally is not needed anymore to install those packages. It is only needed if you have his already downloaded signatures in your pacman-cache. We also updated all the package databases to reflect to the new signatures.
As you can see that we are still able to create daily ISOs the only issue is having those “broken” keys still in our keyring. As soon as all packages got rebuild by a different maintainer or buildserver we can safely also remove the not needed gpg key from our keyring.
Thanks Olli; I just applied it on 3 machines and it worked flawless. 
When people see error messages they tend to assume something is broken, especially when there isn’t anything to indicate otherwise. Your reply is the first to give some actual explanation of the situation.
This. Clarification of issues from the team and project transparency is (from my perspective) an important quality to many people in this sphere. Myself included.
Especially when it’s something as critical as keys and trust etc.