Arch Linux

Noki

Member

Registered: 2018-06-08

Posts: 100

[SOLVED] Sudden Pacman issues (erros mostly around signature)

Hi, I'm rebuilding Arch on my laptop (Windows 10 october update nuked my machine so decided to go for a clean slate). I am at the final step before rebooting without the installation media and got pacman signature errors installing 'grub os-prober efibootmgr'. I've switched to my PC to check there and 'sudo pacman -Syu' and it ran just fine. So I ran it again and boom it was suddenly broken.

Now when I open my terminal it shows this error immediately:

warning: database file for 'core' does not exist (use '-Sy' to download)
warning: database file for 'extra' does not exist (use '-Sy' to download)
warning: database file for 'community' does not exist (use '-Sy' to download)
warning: database file for 'multilib' does not exist (use '-Sy' to download)
warning: database file for 'sublime-text' does not exist (use '-Sy' to download)

So I ran it and got:

sudo pacman -Sy
:: Synchronising package databases...
error: GPGME error: No data
error: failed to update core (invalid or corrupted database (PGP signature))
error: GPGME error: No data
error: failed to update extra (invalid or corrupted database (PGP signature))
error: GPGME error: No data
error: failed to update community (invalid or corrupted database (PGP signature))
error: GPGME error: No data
error: failed to update multilib (invalid or corrupted database (PGP signature))
 sublime-text                                                                 1836.0   B  0.00B/s 00:00 [#############################################################] 100%
 sublime-text.sig                                                              543.0   B  0.00B/s 00:00 [#############################################################] 100%
error: sublime-text: key "F57D4F59BD3DF454" is unknown
:: Import PGP key 4096R/1EDDE2CDFC025D17F6DA9EC0ADAE6AD28A8F901A, "Sublime HQ Pty Ltd <support@sublimetext.com>", created: 2017-05-08? [Y/n] y
error: sublime-text: signature from "Sublime HQ Pty Ltd <support@sublimetext.com>" is unknown trust
error: failed to update sublime-text (invalid or corrupted database (PGP signature))
error: failed to synchronize all databases

Now I tried clearing things out as suggested in some post on this forum like so:

rm -R /etc/pacman.d/gnupg
sudo rm /var/lib/pacman/sync/*db.sig*
sudo rm -R /var/lib/pacman/sync
pacman-key --init
pacman-key --populate archlinux

OUTPUT:

sudo pacman-key --init
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
gpg: Generating pacman keyring master key...
gpg: key 322E25C6578D5202 marked as ultimately trusted
gpg: directory '/etc/pacman.d/gnupg/openpgp-revocs.d' created
gpg: revocation certificate stored as '/etc/pacman.d/gnupg/openpgp-revocs.d/1B905EE218F7B5C5D0E69D81322E25C6578D5202.rev'
gpg: Done
==> Updating trust database...
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u

MORE OUTPUT:

sudo pacman-key --populate archlinux
==> Appending keys from archlinux.gpg...
==> Locally signing trusted keys in keyring...
  -> Locally signing key DDB867B92AA789C165EEFA799B729B06A680C281...
  -> Locally signing key 684148BB25B49E986A4944C55184252D824B18E8...
  -> Locally signing key 91FFE0700E80619CEB73235CA88E23E377514E00...
  -> Locally signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7...
  -> Locally signing key 0E8B644079F599DFC1DDC3973348882F6AC6A4C2...
==> Importing owner trust values...
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: inserting ownertrust of 4
gpg: setting ownertrust to 4
==> Disabling revoked keys in keyring...
  -> Disabling key 7FA647CD89891DEDC060287BB9113D1ED21E1A55...
  -> Disabling key D4DE5ABDE2A7287644EAC7E36D1A9E70E19DAA50...
  -> Disabling key 40440DC037C05620984379A6761FAD69BA06C6A9...
  -> Disabling key B1F2C889CB2CCB2ADA36D963097D629E437520BD...
  -> Disabling key BC1FBE4D2826A0B51E47ED62E2539214C6C11350...
  -> Disabling key 63F395DE2D6398BBE458F281F2DBB4931985A992...
  -> Disabling key 8F76BEEA0289F9E1D3E229C05F946DED983D4366...
  -> Disabling key 4FCF887689C41B09506BE8D5F3E1D5C5D30DB0AD...
  -> Disabling key FB871F0131FEA4FB5A9192B4C8880A6406361833...
  -> Disabling key 81D7F8241DB38BC759C80FCE3A726C6170E80477...
  -> Disabling key 5E7585ADFF106BFFBBA319DC654B877A0864983E...
  -> Disabling key 50F33E2E5B0C3D900424ABE89BDCF497A4BBCC7F...
  -> Disabling key E7210A59715F6940CF9A4E36A001876699AD6E84...
  -> Disabling key 65EEFE022108E2B708CBFCF7F9E712E59AF5F22A...
  -> Disabling key F5A361A3A13554B85E57DDDAAF7EF7873CFD4BB6...
  -> Disabling key 40776A5221EF5AD468A4906D42A1DB15EC133BAD...
  -> Disabling key 8CF934E339CAD8ABF342E822E711306E3C4F88BC...
  -> Disabling key 5696C003B0854206450C8E5BE613C09CB4440678...
  -> Disabling key 9515D8A8EAB88E49BB65EDBCE6B456CAF15447D5...
  -> Disabling key 4A8B17E20B88ACA61860009B5CED81B7C2E5C0D2...
  -> Disabling key 0B20CA1931F5DA3A70D0F8D2EA6836E1AB441196...
  -> Disabling key 34C5D94FE7E7913E86DC427E7FB1A3800C84C0A5...
  -> Disabling key 39F880E50E49A4D11341E8F939E4F17F295AFBF4...
  -> Disabling key 66BD74A036D522F51DD70A3C7F2A16726521E06D...
  -> Disabling key DBE7D3DD8C81D58D0A13D0E76BC26A17B9B7018A...
  -> Disabling key 07DFD3A0BC213FA12EDC217559B3122E2FA915EC...
  -> Disabling key 44D4A033AC140143927397D47EFD567D4C7EA887...
  -> Disabling key 27FFC4769E19F096D41D9265A04F9397CDFD6BB0...
  -> Disabling key 8840BD07FC24CB7CE394A07CCF7037A4F27FB7DA...
==> Updating trust database...
gpg: key 1EB2638FF56C0C53: no user ID for key signature packet of class 10
gpg: key 1EB2638FF56C0C53: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: bad data signature from key 20E8A9C77716EB4F: Wrong key usage (0x19, 0x2)
gpg: depth: 0  valid:   1  signed:   5  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: bad data signature from key 20E8A9C77716EB4F: Wrong key usage (0x19, 0x2)
gpg: depth: 1  valid:   5  signed:  71  trust: 0-, 0q, 0n, 5m, 0f, 0u
gpg: depth: 2  valid:  71  signed:  10  trust: 71-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2018-12-13

I'm not sure what's going on. I was messing with my router settings at the time, but I still have internet just fine. This is the only thing that broke. Can anyone point me in the right direction?

Since my laptop is at a critical point of a clean installation (grub) I would rather get it fixed so I can at least power it off without hassle or forgetting where I am with the installation.

Last edited by Noki (2018-10-06 17:30:25)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,729

Re: [SOLVED] Sudden Pacman issues (erros mostly around signature)

Most of those errors look like a bad mirror.

The key error is for the key from "Sublime HQ Pty Ltd", which is not from Arch but from a 3rd party. Populating the keyring with the Arch keys isn't going to do anything.

Noki

Member

Registered: 2018-06-08

Posts: 100

Re: [SOLVED] Sudden Pacman issues (erros mostly around signature)

Switching mirror on my desktop seem to fix it. Is there a simple way to do this on my laptop with only the terminal. The mirror list is huge by default and the guide I used said to generate it from https://www.archlinux.org/mirrorlist/

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,729

Re: [SOLVED] Sudden Pacman issues (erros mostly around signature)

Actual errors from the laptop would be the first step.

Noki

Member

Registered: 2018-06-08

Posts: 100

Re: [SOLVED] Sudden Pacman issues (erros mostly around signature)

It's cool. I ended up just commenting out some of the mirrors in the list randomly and then ran it again. Seems to have done the trick. I can redo it for the fastest mirror when I have KDE installed. The laptop was showing similar errors and it was much easier to pull these out from my desktop since all the laptop has right now is a terminal.

Thanks for your help, all seems to be well on both machines now.

As a side note, I have 2 internet connections (as of this week). 1 is fast the other super slow. The slow one keeps taking over the network and acting as default internet connection. I was disabling the modem on this router at the time since my download speeds seemed slow. Perhaps this caused the signature error?