Key could not be locally signed

Support Software & Applications
1

I’m currently running into the issue
==> ERROR: 3B794DE6D4320FCE594F4171279E7CF5D8D56EC8 could not be locally signed.
which happens when trying to update
core/manjaro-keyring from 20230318-1 to 20230615-1.

2 Likes
2

Can confirm, the key should be removed but it does not because of the date:

Ah, the key is 2 times in the script also in:


pre_upgrade() {
	if [[ "$(vercmp $2 20220509-2)" -lt 0 ]]; then
		msg "Delete wrongly disabled keys"
		pacman-key -d 688E8F82879D0E25CE541426150C200743ED46D8
		pacman-key -d 3B794DE6D4320FCE594F4171279E7CF5D8D56EC8
3 Likes
3

So how to fix that? Is there going to be an update for the package?

4

Yep, sooner or later

1 Like
5

Any chance to fix that in the meantime to get the error fixed and to be able to install the updates?

6

It’s already been fixed with manjaro-keyring 20230616-3.

7

It still errors here

8

The following solved it for me in the past:

$ sudo rm -rfv /etc/pacman.d/gnupg
$ sudo pacman-key --init
$ sudo pacman-key --populate archlinux
$ sudo pacman-key --populate manjaro
$ sudo pacman -Sy gnupg archlinux-keyring manjaro-keyring
$ sudo pacman -Syyu

thanks to @Zesko

1 Like
9

This didn’t solve it for me, I had to Command out line 45 SigLevel = Required DatabaseOptional in /etc/pacman.conf
and add a line SigLevel = Optional TrustAll run all --init stuff and then after the update toggle line 45 back to normal.

10

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