Ok, I moved (ie reinstalled) day before yesterday to my biggest and fastest SSD using the most current release ISO. I had no issues on the previous install…but…
Since then, I’ve had key issues multiple times a day. I’ve followed the (search) advise to retrieve the key and locally sign it. Next time, I nuked the key database and repopulated it. Today, it’s complaining again. Something has to be wrong on my end, unless everyone else is getting this invalid key error.
Can someone point me in a direction? I’m a compulsive updater and having to retrust the key one to several times a day is not much fun.
How are you installing and updating packages? Usually if you’re using something else than pacman, it can cause keyring issues. (prominent ones are packagekit (discover, etc) and pamac)
1 Like
Usually paru, but occassionally simply pacman 
I just also re rated my mirrors in case that could be an issue.
You can also try clearing your cache
sudo pacman -Scc
Completed. Guess it’s a wait and see now, unless someone else has other suggestions.
Thank you Naim for your suggestions.
1 Like
Hmm, well it’s been 22 hours…I’ll give it another day 
But looking much better so far.
I wonder if there was something off-kilter in the package cache?
I don’t really know. Suspicions are currently something funky with the cdn77 mirror.
I would try that in terminal @Danny_Barron
sudo pacman-key --refresh-keys
Also; & see what it does on your end.
sudo pacman-key --recv-keys F3B607488DB35A47 --keyserver keyserver.ubuntu.com# Sign the repository key
sudo pacman-key --lsign-key F3B607488DB35A47
sudo pacman -Syy archlinux-keyring cachyos-keyring
I did those (day before yesterday) and it error’d again yesterday morning.
Being on arch based distros for oh…seven years, I’ve seen key issues and dealt with them before. I’m just not used to the same key on multiple days lol
That s weird @Danny_Barron , CachyOS s acting weirdly lately update-wise, I would think it s because of the latest Arch updates & the repos that might be out of sync.
Well still good, seems clearing the cache did the trick.
1 Like