Fresh install Keyring error

[HeroTch]

IMPORTANT
Please read README and Docs before creating the issue.

Please fill out the below information:
Describe the issue
A clear and concise description of what the bug is.

Fresh install, starting Arch.exe

Initialize keyring...
gpg: /etc/pacman.d/gnupg/trustdb.gpg: trustdb created
gpg: no ultimately trusted keys found
gpg: starting migration from earlier GnuPG versions
gpg: porting secret keys from '/etc/pacman.d/gnupg/secring.gpg' to gpg-agent
gpg: migration succeeded
==> Generating pacman master key. This may take some time.
gpg: Generating pacman keyring master key...
gpg: agent_genkey failed: No such file or directory
gpg: key generation failed: No such file or directory
gpg: Done
==> Updating trust database...
gpg: no need for a trustdb check

after multiple retries, directly into the shell
manually run pacman-key --init same error

To Reproduce
Steps to reproduce the behavior:

1. Fresh install

Expected behavior
A clear and concise description of what you expected to happen.

can use pacman correctly

Screenshots
If applicable, add screenshots to help explain your problem.

Enviroment:

• Windows build number: 10.0.22621.1555
• Security Software: Windows Defender
• WSL version 1/2: WSL 2
• ArchWSL version: 22.10.16.0
• ArchWSL Installer type zip/appx/other clean/update: zip / scoop same error
• Launcher version: 22020900

Additional context
Add any other context about the problem here.

wsl --version

WSL 版本： 1.2.1.0
内核版本： 5.15.90.1
WSLg 版本： 1.0.51
MSRDC 版本： 1.2.3770
Direct3D 版本： 1.608.2-61064218
DXCore 版本： 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows 版本： 10.0.22621.1555

[cquick01]

I saw the same issue, but the following workaround fixed it for me.

You should be able to hit ctrl-c then run the following commands (as root) to reinitialize the keyring

killall gpg-agent
rm -rf /etc/pacman.d/gnupg/
pacman-key --init
pacman-key --populate archlinux
pacman -Sy archlinux-keyring
pacman -Syu  # upgrades work as expected, and no more gpg errors on startup

[foundObjects]

I saw the same issue, but the following workaround fixed it for me.

You should be able to hit ctrl-c then run the following commands (as root) to reinitialize the keyring

killall gpg-agent
rm -rf /etc/pacman.d/gnupg/
pacman-key --init
pacman-key --populate archlinux
pacman -S archlinux-keyring
pacman -Syu  # upgrades work as expected, and no more gpg errors on startup

Small note on the above, I had to use

pacman -Sy archlinux-keyring

rather than -S

[Dynge]

I saw the same issue, but the following workaround fixed it for me.
You should be able to hit ctrl-c then run the following commands (as root) to reinitialize the keyring

killall gpg-agent
rm -rf /etc/pacman.d/gnupg/
pacman-key --init
pacman-key --populate archlinux
pacman -S archlinux-keyring
pacman -Syu  # upgrades work as expected, and no more gpg errors on startup

Small note on the above, I had to use

pacman -Sy archlinux-keyring

rather than -S

Same here.

Got the following error with just -S:

[foundObjects]

Yeah, pacman -S <package> will try to fetch whatever version of the package is known in your cached package list without checking for a new version. You need to run pacman -Sy archlinux-keyring to fetch an updated package list and the current version.

Always make sure to run pacman -Su after an -Sy, you can break things in surprising ways if you leave the system partially upgraded.

[cquick01]

Sorry for the confusion. I must have updated the cache beforehand by attempting a full upgrade. Fixed the comment 👍

[angelside]

This error still exists on the very first start.

[jthoward64]

This error still exists on the very first start.

Reproduced on Windows 11 (22635.2850)

[cquick01]

This still seems to be an issue on first boot, although there is a post-boot workaround. Just tried to build from source using the latest tags and the same issue occurred on boot.

[ruizlenato]

I saw the same issue, but the following workaround fixed it for me.

You should be able to hit ctrl-c then run the following commands (as root) to reinitialize the keyring

killall gpg-agent
rm -rf /etc/pacman.d/gnupg/
pacman-key --init
pacman-key --populate archlinux
pacman -Sy archlinux-keyring
pacman -Syu  # upgrades work as expected, and no more gpg errors on startup

Initialize keyring...
/usr/bin/bash: /usr/lib/libc.so.6: version `GLIBC_2.38' not found (required by /usr/bin/bash)
/usr/bin/bash: /usr/lib/libc.so.6: version `GLIBC_2.38' not found (required by /usr/lib/libreadline.so.8)|

After I did that, I now get this error.

[MisileLab]

I saw the same issue, but the following workaround fixed it for me.
You should be able to hit ctrl-c then run the following commands (as root) to reinitialize the keyring

killall gpg-agent
rm -rf /etc/pacman.d/gnupg/
pacman-key --init
pacman-key --populate archlinux
pacman -Sy archlinux-keyring
pacman -Syu  # upgrades work as expected, and no more gpg errors on startup

Initialize keyring...
/usr/bin/bash: /usr/lib/libc.so.6: version `GLIBC_2.38' not found (required by /usr/bin/bash)
/usr/bin/bash: /usr/lib/libc.so.6: version `GLIBC_2.38' not found (required by /usr/lib/libreadline.so.8)|

After I did that, I now get this error.

you can use sudo pacman -S glibc for fix this

[DeltaRazero]

I saw the same issue, but the following workaround fixed it for me.
You should be able to hit ctrl-c then run the following commands (as root) to reinitialize the keyring

killall gpg-agent
rm -rf /etc/pacman.d/gnupg/
pacman-key --init
pacman-key --populate archlinux
pacman -Sy archlinux-keyring
pacman -Syu  # upgrades work as expected, and no more gpg errors on startup

Initialize keyring...
/usr/bin/bash: /usr/lib/libc.so.6: version `GLIBC_2.38' not found (required by /usr/bin/bash)
/usr/bin/bash: /usr/lib/libc.so.6: version `GLIBC_2.38' not found (required by /usr/lib/libreadline.so.8)|

After I did that, I now get this error.

you can use sudo pacman -S glibc for fix this

That doesn't work anymore since it now installs glib 2.39 instead. Basically it's impossible to do a fresh install anymore.