Maybe you forgot to delete old keys? Or to init? Why don’t you post the commands and output from your terminal. Just start a new, then grab everything and paste it in code tags.
This looks like an clock issue - a dead cmos battery on 10y old mainboard?
Of course - taking into account - the nature of the entire topic - it is not conclusive - but it sure looks like it.
And the buildkey
I have tested the commands for resetting the keyrings - several times - open a terminal and execute - in order the following excerpt from my test vm - of course if you read this thread in 6months from 2023-06-16T22:00:00Z the filenames will be different
Resetting the keys works fine by me after the 16-3 version. The last time i did it according to the corrected version of the old wiki, which was essentially the new wiki. To sum up: i did not use --refresh-keys.
The time issue occured on my previous attempts with --refresh keys. I do not thik its was that good of a decision that command so i did not do it after the newest reset. Explanation: it run about 15 minutes, it contacted dosens of servers, some of them unreachable, it deleted dosens of cetrificates, it added dosens new, and it trew error on another dosen, so it basically just messes the things up.
I can try again if you want just for the sake of debugging (just tell me again the command because is not in the wiki anymore).
The laptop is 1 month old, the battery should be fine. And the first thing was to install ntp. I am dual booting with windows however, so it messes the clock from UTC to RTC after rebooting (GMT+2 DST, so it can be 2 hours off after rebooting, but it was not yesterday).
But 2 hours are not 3000 days…
So i don’t want to use the word bug again but it seems a little like it. There is probably some certificate with messed date, from the dosens that are fetched from who knows where with -refresh command.
In my test there was no need to execute other commands.
[fh@lxqt ~]$ pacman-mirrors
Pacman-mirrors version 4.23.2
Local mirror status for stable branch
Mirror #1 OK 00:17 Austria https://mirror.easyname.at/manjaro/
After the reset described - pacman functioned as expected
[fh@lxqt ~]$ sudo pacman -Syyu
:: Synchronizing package databases...
core 143,6 KiB 756 KiB/s 00:00 [-----------------] 100%
extra 1636,8 KiB 3,61 MiB/s 00:00 [-----------------] 100%
multilib 145,5 KiB 674 KiB/s 00:00 [-----------------] 100%
:: Starting full system upgrade...
there is nothing to do
again but it seems a little like it. There is probably some certificate with messed date, from the dosens that are fetched from who knows where with -refresh command.