Can not update due to issue with keyrings

[samiVami]

I can't post the output becuase it has the links to the keys and I have a max of 5 links.

The point is :

error: key "Christian Rebischke (Archlinux Security Team-Member) <chris.rebischke@archlinux.org>" could not be imported
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.

What I tried to :
reinstalling archlinux-keyring : did not work
This is what I get

sudo pacman -S archlinux-keyring 
warning: archlinux-keyring-20220125-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) archlinux-keyring-20220125-1

Total Download Size:   1,01 MiB
Total Installed Size:  1,43 MiB
Net Upgrade Size:      0,00 MiB

:: Proceed with installation? [Y/n]
:: Retrieving packages...
archlinux-keyring-20220125-1-any                                                                                   1036,5 KiB  5,01 MiB/s 00:00 [----------------------------------------------------------------------------------------] 100%
(1/1) checking keys in keyring                                                                                                                   [----------------------------------------------------------------------------------------] 100%
(1/1) checking package integrity                                                                                                                 [----------------------------------------------------------------------------------------] 100%
error: archlinux-keyring: signature from "Christian Hesse <eworm@archlinux.org>" is unknown trust
:: File /var/cache/pacman/pkg/archlinux-keyring-20220125-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.

refreshing the keys : did not work
At some point it halts

gpg: keydb_search failed: Invalid packet
gpg: [don't know]: invalid packet (ctb=00)
gpg: keydb_search failed: Invalid packet
gpg: [don't know]: invalid packet (ctb=00)
gpg: keydb_search failed: Invalid packet
gpg: [don't know]: invalid packet (ctb=00)
gpg: keydb_search failed: Invalid packet
gpg: [don't know]: invalid packet (ctb=00)
gpg: keydb_search failed: Invalid packet
gpg: [don't know]: invalid packet (ctb=00)
gpg: keyring_get_keyblock: read error: Invalid packet
gpg: keyring_get_keyblock failed: Invalid keyring
gpg: failed to rebuild keyring cache: Invalid keyring
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: [don't know]: invalid packet (ctb=00)
gpg: keyring_get_keyblock: read error: Invalid packet
gpg: keydb_get_keyblock failed: Invalid keyring
gpg: validate_key_list failed
gpg: error retrieving 'lains@riseup.net' via WKD: No data
gpg: error reading key: No data
gpg: [don't know]: invalid packet (ctb=00)
gpg: keyserver refresh failed: Invalid packet
==> ERROR: Could not update key: 46F633CBB0EB4BF2</ins>

[TilliDie]

Welcome

Please provide your

garuda-inxi

[samiVami]

@TilliDie

garuda-inxi

System:
  Kernel: 5.16.3-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=0c9822eb-18ec-4e24-9d9b-7685031e8127 rw rootflags=subvol=@
    amd_iommu=on iommu=pt quiet splash rd.udev.log_priority=3
    vt.global_cursor_default=0 systemd.unified_cgroup_hierarchy=1 loglevel=3
  Desktop: i3 4.16.1-191-gb521c18c info: i3bar vt: 7 dm: LightDM 1.30.0
    Distro: Garuda Linux base: Arch Linux
CPU:
  Info: model: AMD Ryzen 7 PRO 4750U with Radeon Graphics bits: 64
    type: MT MCP arch: Zen 2 family: 0x17 (23) model-id: 0x60 (96) stepping: 1
    microcode: 0x8600106
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
    L3: 8 MiB desc: 2x4 MiB
  Speed (MHz): avg: 1402 high: 1494 min/max: 1400/1700 boost: enabled
    scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 1494 2: 1397
    3: 1396 4: 1397 5: 1397 6: 1395 7: 1397 8: 1395 9: 1397 10: 1397 11: 1398
    12: 1397 13: 1397 14: 1397 15: 1397 16: 1397 bogomips: 54298
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional,
    IBRS_FW, STIBP: conditional, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Drives:
  Local Storage: total: 953.87 GiB used: 198.31 GiB (20.8%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: SK Hynix
    model: HFS001TD9TNI-L2B0B size: 953.87 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 11720C10 temp: 30.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 293.57 GiB size: 293.57 GiB (100.00%)
    used: 198.28 GiB (67.5%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
  ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%)
    used: 32.1 MiB (12.5%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 293.57 GiB size: 293.57 GiB (100.00%)
    used: 198.28 GiB (67.5%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
  ID-4: /var/log raw-size: 293.57 GiB size: 293.57 GiB (100.00%)
    used: 198.28 GiB (67.5%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
  ID-5: /var/tmp raw-size: 293.57 GiB size: 293.57 GiB (100.00%)
    used: 198.28 GiB (67.5%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 30.58 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 42.0 C mobo: N/A gpu: amdgpu temp: 42.0 C
  Fan Speeds (RPM): fan-1: 0
Info:
  Processes: 425 Uptime: 3h 13m wakeups: 1 Memory: 30.58 GiB
  used: 6.96 GiB (22.7%) Init: systemd v: 250 tool: systemctl Compilers:
  gcc: 11.1.0 clang: 13.0.0 Packages: 1553 pacman: 1535 lib: 366 flatpak: 18
  Shell: Zsh v: 5.8 running-in: kitty inxi: 3.3.12
Garuda:
  System install date:     2021-12-14
  Last full system update: 2022-02-12
  Is partially upgraded:   Yes
  Using TLP:               No
  Windows dual boot:       Probably (Run as root to verify)
  Snapshots:               Snapper

[TilliDie]

Try

garuda-update

in terminal

[samiVami]

@TilliDie

garuda-update

This is the stderr:

error: failed retrieving file 'chaotic-aur.db' from geo-mirror.chaotic.cx : The requested URL returned error: 404
error: key "Nico Jensch (Chaotic-AUR) <dr460nf1r3@garudalinux.org>" could not be imported
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
[2022-02-19 01:15:58] WARNING: failed to rate http(s) download (https://archmirror.it/repos/community/os/x86_64/community.db): HTTP Error 403: Forbidden
[2022-02-19 01:15:58] WARNING: failed to rate http(s) download (https://mirror.cyberbits.asia/archlinux/community/os/x86_64/community.db): <urlopen error [Errno 101] Network is unreachable>
error: failed retrieving file 'chaotic-aur.db' from geo-mirror.chaotic.cx : The requested URL returned error: 404
error: key "Nico Jensch (Chaotic-AUR) <dr460nf1r3@garudalinux.org>" could not be imported
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
warning: archlinux-keyring-20220125-1 is up to date -- skipping
error: key "Nico Jensch (Chaotic-AUR) <dr460nf1r3@garudalinux.org>" could not be imported
error: required key missing from keyring
error: failed to commit transaction (unexpected error)

[samiVami]

full output:

 garuda-update           
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
 chaotic-aur is up to date
error: failed retrieving file 'chaotic-aur.db' from geo-mirror.chaotic.cx : The requested URL returned error: 404
resolving dependencies...
looking for conflicting packages...

Packages (1) garuda-update-2.0.6-1

Total Installed Size:  0,01 MiB
Net Upgrade Size:      0,00 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                                          [----------------------------------------] 100%
downloading required keys...
:: Import PGP key 0706B90D37D9B881, "Chaotic-AUR Wild Bear Node <wildbear.node@chaotic.cx>"? [Y/n] 
error: key "Nico Jensch (Chaotic-AUR) <dr460nf1r3@garudalinux.org>" could not be imported
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.

--> Refreshing mirrorlists using reflector, please be patient..
[2022-02-19 01:17:25] WARNING: failed to rate http(s) download (<archmirror>.it/repos/community/os/x86_64/community.db): HTTP Error 403: Forbidden
[2022-02-19 01:17:26] WARNING: failed to rate http(s) download (mirror.cyberbits.asia/archlinux/community/os/x86_64/community.db): <urlopen error [Errno 101] Network is unreachable>
################################################################################
################# Arch Linux mirrorlist generated by Reflector #################
################################################################################

# With:       reflector --latest 5 --age 2 --fastest 5 --protocol https --sort rate --save /etc/pacman.d/mirrorlist
# When:       2022-02-19 00:17:26 UTC
# From:       <archlinux>.org/mirrors/status/json/
# Retrieved:  2022-02-19 00:15:11 UTC
# Last Check: 2022-02-18 23:51:43 UTC
// links below are modifed
Server = <>.mirror.chaoticum.net/arch/$repo/os/$arch
Server = mirror.cyberbits.eu/archlinux/$repo/os/$arch
Server = <>.phinau.de/arch/$repo/os/$arch
Server = archmirror.it/repos/$repo/os/$arch
Server = mirror.cyberbits.asia/archlinux/$repo/os/$arch

:: Synchronizing package databases...
 core                                       133,4 KiB   677 KiB/s 00:00 [----------------------------------------] 100%
 extra                                     1542,2 KiB  1396 KiB/s 00:01 [----------------------------------------] 100%
 community                                    6,1 MiB  1450 KiB/s 00:04 [----------------------------------------] 100%
 multilib                                   149,6 KiB   629 KiB/s 00:00 [----------------------------------------] 100%
 chaotic-aur                               1781,2 KiB  2,20 MiB/s 00:01 [----------------------------------------] 100%
error: failed retrieving file 'chaotic-aur.db' from geo-mirror.chaotic.cx : The requested URL returned error: 404
resolving dependencies...
looking for conflicting packages...

Packages (1) garuda-update-2.0.6-1

Total Installed Size:  0,01 MiB
Net Upgrade Size:      0,00 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                                          [----------------------------------------] 100%
downloading required keys...
:: Import PGP key 0706B90D37D9B881, "Chaotic-AUR Wild Bear Node <wildbear.node@chaotic.cx>"? [Y/n] 
error: key "Nico Jensch (Chaotic-AUR) <dr460nf1r3@garudalinux.org>" could not be imported
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.

--> Applying keyring updates before starting full system update..
warning: archlinux-keyring-20220125-1 is up to date -- skipping
resolving dependencies...
looking for conflicting packages...

Packages (2) chaotic-keyring-20220130-1  garuda-hotfixes-1.1.1-1

Total Installed Size:  0,02 MiB
Net Upgrade Size:      0,00 MiB

:: Proceed with installation? [Y/n] 
(2/2) checking keys in keyring                                          [----------------------------------------] 100%
downloading required keys...
:: Import PGP key 0706B90D37D9B881, "Nico Jensch <dr460nf1r3@chaotic.cx>"? [Y/n] 
error: key "Nico Jensch (Chaotic-AUR) <<>/dr460nf1r3@garudalinux.org>" could not be imported
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.

[TNE]

Heyo, this command should fix your issue:
update remote keyring
Let me know if that works.

[SGS]

Please read

How to write a nicely formatted post in Discourse/Forum

Writing a well formatted post in the forum (Discource powered) is important, if you want readers to easily read and understand. It's especially important for terminal output. Here is a brief tutorial. Terminal output For terminal output, text output with special characters, always use code wrapping (Pre-formated text). Select all of the text and do one of these: Hit the </> button in Discource Post Toolbar. Press CtrlShift+C on your keyboard. Manually with markdown After you Copy yo…

Non-formatted terminal outputs are a pain, not only on the smartphone or tablet where you scroll yourself to death.

[samiVami]

This indeed fixed it. Thank you so much!

I have never had this problem. I guess because this time I did not update the system for a long time ?
Could you please explain what it did / why the problem occurred ?

[tbg]

Please do not cross post your issues on the Arch Linux forum.

In case you missed it there is a very prominent notice stickied at the top of the Newbies forum where you posted here:

@tbg

If you are unfamiliar with Arch based distros there are a few things you might not be aware of. Garuda is based on Arch, but this does not mean it is exactly the same as Arch Linux. While Garuda is similar to Arch, this does not mean you are free to post your Garuda help issues on the Arch forum. There are several reasons for this.

Even though Garuda tracks very closely with upstream Arch, there are many Garuda specific packages that a standard Arch install does not contain. Therefore, asking for support on the Arch forum will lead to nothing but confusion for those attempting to provide support there. The Arch forum support staff does not want to deal with the confusion created by a myriad of other derivative distro users asking for help on the Arch forum.

For this reason it has been a long standing Arch forum rule that no users of derivitave distros are permitted to post issues on the Arch Linux forum.

The Arch rule states:

These boards are for the support of Arch Linux, and Arch ONLY

If you have installed Archbang, Antergos, Chakra, Evo/Lution, Manjaro, Whatever, you are NOT running Arch Linux. Similarly, if you followed some random video on YouTube or used an automated script you found on a blog, you are NOT running Arch Linux, so do not expect any support, sympathy or anything but your thread being closed and told to move along.

Arch is a DIY distro: if someone else has done it for you, then showing up here asking to have your hand held for more help is just help vampirism and is not welcome.

Anyone who registers on the Arch forum must agree to adhere to this rule when they open an Arch forum account.

As our Distro attracts more and more users, our forums have become very busy. We try our best to help all users with problems in a timely manner. However, we only have a small number of people assisting on our forum. It may take some time to get your issue addressed here, but that still does not justify violating the Arch furum rules. Recently a disturbing trend has started to occur. More and more Garuda users impatient for an answer on the Garuda forum are opening help requests on the Arch forum as well.

This reflects very poorly on Garuda, that our users are repeatedly violating rules at the Arch forum. For this reason anyone found to be posting Garuda issues on the Arch Linux forum will be receiving a warning from the Garuda moderation staff in an effort to curb this behavior.

We have nothing but respect and admiration for the Arch Linux distro here, and would like our users to respect their forum rules as well as ours. Please never post Garuda issues on the Arch Linux forum.

Your cooperation in this matter would be greatly appreciated.

Do not post your Garuda issues on the Arch forum.