What I can not check now anymore is that reinstalling the archlinux-keyring would probably have fixed this without initializing and populating it. Will try that next time.
sudo pacman-key --init
sudo pacman-key --populate archlinux
If necessary this one
sudo pacman-key --refresh-keys
In our example this eventually helped. I remember on my other ssd there was an update of this one. Keep track of this one when updating.
Keep also track of the ‘linux’ package. That is your kernel. Reboot afterwards.
sudo pacman -S archlinux-keyring
Sources for you to check
There you can read this :
There are multiple possible sources of this problem:
- An outdatedpackage.
- Incorrect date.
- Your ISP blocked the port used to import PGP keys.
- Your pacman cache contains copy of unsigned packages from previous attempts.
dirmngris not correctly configured
In addition I found a news post that can also be useful in this situation and other situations regarding the pacman-key.
“In addition, we recommend installing haveged, a daemon that generates system entropy; this speeds up critical operations in cryptographic programs such as gnupg (including the generation of new keyrings).”
For the record I did not do this and everything was speedy enough and haveged.service was not enabled.
12345678 sudo pacman -Syu havegedsudo systemctl start havegedsudo systemctl enable havegedsudo rm -fr /etc/pacman.d/gnupgsudo pacman-key --initsudo pacman-key --populate archlinuxsudo systemctl stop haveged