Update does not proceed - "error: starship-git: signature from "Nico Jensch <dr460nf1r3@garudalinux.org>" is unknown trust"

Issues & Assistance
#1

Here is what i get after sudo pacman -Syyu

Blockquote

:: Synchronising package databases...
core 131,5 KiB 465 KiB/s 00:00 [--------------------------------------------------------------------] 100%
extra 1601,4 KiB 3,92 MiB/s 00:00 [--------------------------------------------------------------------] 100%
community 5,5 MiB 4,78 MiB/s 00:01 [--------------------------------------------------------------------] 100%
multilib 150,4 KiB 147 MiB/s 00:00 [--------------------------------------------------------------------] 100%
chaotic-aur 1022,3 KiB 1398 KiB/s 00:01 [--------------------------------------------------------------------] 100%
:: Starting full system upgrade...
warning: gesture-manager-x-git: local (0.1-1) is newer than chaotic-aur (r9.ce6f7d0-1)
warning: libldac: local (2.0.2.3-3) is newer than extra (2.0.2.3-1)
:: Replace python-dbus with extra/dbus-python? [Y/n] y
:: Replace python-dbus-common with extra/dbus-python? [Y/n] y
resolving dependencies...
looking for conflicting packages...
:: nohang and nohang-git are in conflict. Remove nohang-git? [y/N] y
:: dbus-python and python2-dbus are in conflict. Remove python2-dbus? [y/N] y
warning: dependency cycle detected:
warning: mesa will be installed before its libglvnd dependency
warning: dependency cycle detected:
warning: nvidia-utils will be installed before its libglvnd dependency
warning: dependency cycle detected:
warning: xorg-server will be installed before its libglvnd dependency
warning: dependency cycle detected:
warning: nvidia-utils will be installed before its libglvnd dependency
warning: dependency cycle detected:
warning: smbclient will be installed before its cifs-utils dependency

Blockquote

Total Download Size: 3,35 MiB
Total Installed Size: 6457,33 MiB
Net Upgrade Size: 183,83 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
starship-git-0.52.1.1525.g5758abf1-1-x86_64 3,3 MiB 9,41 MiB/s 00:00 [--------------------------------------------------------------------] 100%
(455/455) checking keys in keyring [--------------------------------------------------------------------] 100%
(455/455) checking package integrity [--------------------------------------------------------------------] 100%
error: starship-git: signature from "Nico Jensch dr460nf1r3@garudalinux.org" is unknown trust
:: File /var/cache/pacman/pkg/starship-git-0.52.1.1525.g5758abf1-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: failed to commit transaction (invalid or corrupted package)
Errors occurred, no packages were upgraded.

Blockquote

I have tried already:

sudo pacman -Sy archlinux-keyring
sudo pacman-key --populate archlinux
sudo pacman-key --refresh-keys
sudo pacman -Syu

Thanks in advance! (and why did this breakage happen actually?)
#2

Good first try, it was the right thing to do - you just missed one little thing: starship-git a Chaotic-AUR package rather than an Archlinux one so we need to populate chaotic-aur instead of archlinux.
Afaik, you could also simply use the Garuda Assisstants "refresh keyring" option to fix this.

Its not really a breakage, it just seems to me that you didnt update your system for a some time - in this time a new signing key for packages was introduced which your system does not know yet. chaotic-keyring is the package in which the keys are shipped. As this package is not installed before all others the signature is still invalid at the time of updating.

3 Likes
#3

Yes, it has been like a month since i updated.

sudo pacman-key --populate chaotic (gave me) :

Blockquote

==> Appending keys from chaotic.gpg...
==> Locally signing trusted keys in keyring...
-> Locally signing key EF925EA60F33D0CB85C44AD13056513887B78AEB...
==> Importing owner trust values...
==> Updating trust database...
gpg: next trustdb check due at 2021-08-02

Then sudo pacman -Syyu

:: Starting full system upgrade...
warning: gesture-manager-x-git: local (0.1-1) is newer than chaotic-aur (r9.ce6f7d0-1)
warning: libldac: local (2.0.2.3-3) is newer than extra (2.0.2.3-1)
:: Replace python-dbus with extra/dbus-python? [Y/n] y
:: Replace python-dbus-common with extra/dbus-python? [Y/n] y
resolving dependencies...
looking for conflicting packages...
:: nohang and nohang-git are in conflict. Remove nohang-git? [y/N] y
:: dbus-python and python2-dbus are in conflict. Remove python2-dbus? [y/N] y
warning: dependency cycle detected:
warning: mesa will be installed before its libglvnd dependency
warning: dependency cycle detected:
warning: nvidia-utils will be installed before its libglvnd dependency
warning: dependency cycle detected:
warning: xorg-server will be installed before its libglvnd dependency
warning: dependency cycle detected:
warning: nvidia-utils will be installed before its libglvnd dependency
warning: dependency cycle detected:
warning: smbclient will be installed before its cifs-utils dependency

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
starship-git-0.52.1.1525.g5758abf1-1-x86_64 3,3 MiB 5,27 MiB/s 00:01 [--------------------------------------------------------------------] 100%
(455/455) checking keys in keyring [--------------------------------------------------------------------] 100%
(455/455) checking package integrity [--------------------------------------------------------------------] 100%
error: starship-git: signature from "Nico Jensch dr460nf1r3@garudalinux.org" is unknown trust
:: File /var/cache/pacman/pkg/starship-git-0.52.1.1525.g5758abf1-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: failed to commit transaction (invalid or corrupted package)
Errors occurred, no packages were upgraded.

Blockquote

So i think the result is the same. Should i answer no instead of yes, to that query? The update does not proceed. What could be the problem here?

#4

Just do a

sudo pacman -Sy chaotic-keyring

and then update afterwards. The keyring package needs to be updated before populating the keyring :eyes:
(notice that usually -Sy is not good practice as it might result in a partial upgrade, in this case however we only need the keyring updated before everything else)

5 Likes
#5

Yes, now it went through:

Starship-git-0.52.1.1525.g5758abf1-1-x86_64 3,3 MiB 2,46 MiB/s 00:01 [--------------------------------------------------------------------] 100%

All upgrading! Thank you very much for your help and patience! I'll put these procedures up some place, so i can right away help others upon same issue.

I wonder what this Starship-git is? Could the problem had been solved by removing this source / app or so? I don't have anything too precious installed.

1 Like
#6

Its the prompt of our terminals :slight_smile: I guess you will run into these as well after updating:

2 Likes
#7

Ok! So if i do run into those, what's the course of action there? :zipper_mouth_face:

1 Like
#8

As a general rule, more frequent updates will assist in having less errors when updating. Just FYI.

5 Likes
#9

https://forum.garudalinux.org/t/manual-intervention-required-starship/4320

5 Likes
#10

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.