Arch Linux

s1nistr4

Member

Registered: 2023-08-25

Posts: 3

11 32 12

.

Last edited by s1nistr4 (2024-10-02 19:05:36)

seth

Member

Registered: 2012-09-03

Posts: 61,601

Re: 11 32 12

The latest iso is from August 1st so if this was a problem w/ the iso, it'd have been so for more than 3 weeks now.
Yet you're the first one to "report" that…

bam keyring errors. It seems it can't contact the keyring servers … ton of EOF errors, as well as unable to register keyring errors

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855

And try to

pacman -Sy archlinux-keyring

ahead of everything, but we better look at the actual errors first.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

s1nistr4

Member

Registered: 2023-08-25

Posts: 3

Re: 11 32 12

1

Last edited by s1nistr4 (2024-10-02 19:05:57)

schard

Forum Moderator

From: Hannover

Registered: 2016-05-06

Posts: 2,191

Website

Re: 11 32 12

Did you run

pacman-key --populate archlinux

?

---

Inofficial first vice president of the Rust Evangelism Strike Force

seth

Member

Registered: 2012-09-03

Posts: 61,601

Re: 11 32 12

it should work ootb anyway

Yes "should" …
You otoh should post the actual errors, not vague descriptions thereof.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

WorMzy

Administrator

From: Scotland

Registered: 2010-06-16

Posts: 12,644

Website

Re: 11 32 12

Works fine here.

---

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

s1nistr4

Member

Registered: 2023-08-25

Posts: 3

Re: 11 32 12

1

Last edited by s1nistr4 (2024-10-02 19:06:06)

mpan

Member

Registered: 2012-08-01

Posts: 1,378

Website

Re: 11 32 12

Being offensive is not making getting help easier. Even worse, if the accusations are in disagreement both with actual observations and with your own report.

Speaking of which, I want to bring to attention, that s1nistr4 claims they already installed the system with no errors. Keyring or otherwise:

4. Ran ```pacstrap /mnt base base-devel linux linux-firmware```
5. arch-chrooted into the /mnt partition after it was done

I would say this indicates the ISO worked fine.

s1nistr4: you were asked twice to provide the exact error messages. Please do this. Also please provide the exact command, which you invoked to get the error. Do not paraphrase, do not describe what you believe you saw: just provide the error message.

---

Sometimes I seem a bit harsh — don’t get offended too easily!

Tammit9

Member

Registered: 2023-08-26

Posts: 2

Re: 11 32 12

This is happening to me too. I'll create a separate post once I've done some troubleshooting, but I wanted to quickly confirm that this is definitely affecting more than one person.

Last edited by Tammit9 (2023-08-26 01:20:19)

Tammit9

Member

Registered: 2023-08-26

Posts: 2

Re: 11 32 12

The same errors happened to me this morning doing a routine system update with pacman -Syu

Running the steps in https://wiki.archlinux.org/title/Pacman … leshooting worked for me, including removing the /etc/pacman.d/gnupg directory

Previously running pacman-key --init and pacman-key --populate without remove the gnupg dir didn't fix the issue

I don't understand what happened but I'm guessing it was related to the fact that archlinux-keyring was one of the packages requiring an update

mpan

Member

Registered: 2012-08-01

Posts: 1,378

Website

Re: 11 32 12

Hello Tammit9 and welcome to Arch fora! Keyring issues come in various flavors. It may be the same or it may be not, but until OP decides to share the exact errors we can’t tell.

I just tested it with August ISO and encountered no problems. Neither with pacstrap nor while running `pacman -S` inside the chroot.

A few days ago archlinux-keyring received an update, which shifts expiration of one key and adds another. Using an older version could hypothetically cause trouble, but the package itself would still be updateable and the failure would already occur in pacstrap. This doesn’t fit the OP’s description.

What puzzles me is the omission of the -K flag in pacstrap invocation

---

Sometimes I seem a bit harsh — don’t get offended too easily!

seth

Member

Registered: 2012-09-03

Posts: 61,601

Re: 11 32 12

@Tammit9, you were running this from an installed system, not the August iso, right?
Check your pacman log for your previous update, as suggested by mpan you might have skipped a couple of updates and ran into a dated key before the archlinux-keyring-wkd-sync.timer hit (If you boot the system very rarely?)

including removing the /etc/pacman.d/gnupg directory

You might also have configured a custom keyserver that's now out of business? (Do you still have the files?)

As for the OP, there could be network issues, a locally broken iso (bad usb key) or the system time severely off. Or the gods hate him. Or the local dictator has an extended episode of severe insecurity complexes (what perhaps falls under "network issues")
We don't know because there's no actual error data.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

wavepass

Member

Registered: 2023-08-26

Posts: 1

Re: 11 32 12

Did you install network manager or dhcpcd?
Try

pacstrap -K /mnt base linux linux-firmware dhcpcd

Is

ping archlinux.org

working?

Last edited by wavepass (2023-08-26 22:19:28)