You are not logged in.

#1 2014-12-19 21:58:55

ayr0
Member
Registered: 2010-08-12
Posts: 93

[SOLVED] Pacman refuses to upgrade due to missing key

Starting today, I get this error messge when trying to upgrade via pacman

error: key "7A4E76095D8A52E4" could not be looked up remotely
error: required key missing from keyring
error: failed to commit transaction (unexpected error)

Generating a fresh keyring (https://www.archlinux.org/news/gnupg-21 … n-keyring/) doesn't resolve the problem.
Anyone else getting an error similar to this?
Any ideas on resolving the issue?

Last edited by ayr0 (2014-12-19 22:06:18)

Offline

#2 2014-12-19 22:06:06

ayr0
Member
Registered: 2010-08-12
Posts: 93

Re: [SOLVED] Pacman refuses to upgrade due to missing key

Solved by reinstalling archlinux-keyring

Offline

#3 2014-12-21 00:00:02

mélodie
Member
From: France
Registered: 2006-12-31
Posts: 18
Website

Re: [SOLVED] Pacman refuses to upgrade due to missing key

I followed your lead. Thanks, I solved it too! big_smile

Offline

#4 2014-12-23 12:23:07

kozaki
Member
From: London >. < Paris
Registered: 2005-06-13
Posts: 670
Website

Re: [SOLVED] Pacman refuses to upgrade due to missing key

One should follow https://wiki.archlinux.org/index.php/Pa … mport_keys in case reinstalling pacman-keyring wouldn't sufice.

Using unofficial repos? May have a sig-key, which may need to be re-added. https://wiki.archlinux.org/index.php/Un … positories
eg for Graysky's repo-ck: https://bbs.archlinux.org/viewtopic.php … 1#p1485841


Seeded last month: Arch 50 gig, derivatives 1 gig
Desktop @3.3GHz 8 gig RAM, linux-ck
laptop #1 Atom 2 gig RAM, Arch linux stock i686 (6H w/ 6yrs old battery smile) #2: ARM Tegra K1, 4 gig RAM, ChrOS
Atom Z520 2 gig RAM, OMV (Debian 7) kernel 3.16 bpo on SDHC | PGP Key: 0xFF0157D9

Offline

#5 2014-12-27 20:38:46

Doctor Drive
Member
From: Ukraine
Registered: 2010-08-11
Posts: 167
Website

Re: [SOLVED] Pacman refuses to upgrade due to missing key

ayr0 wrote:

Solved by reinstalling archlinux-keyring

Actually it was an upgrade. I guess you should always update archlinux-keyring first. Thanks for pointing it out.

Offline

#6 2015-01-23 22:23:05

ElectricPrism
Member
Registered: 2012-12-07
Posts: 33

Re: [SOLVED] Pacman refuses to upgrade due to missing key

sudo pacman -S archlinux-keyring && sudo pacman -Syu

@ayr0 - Thanks, re-installing archlinux-keyring worked.

Offline

#7 2015-03-08 03:54:20

rajat
Member
Registered: 2013-10-10
Posts: 10

Re: [SOLVED] Pacman refuses to upgrade due to missing key

sudo pacman -S archlinux-keyring && sudo pacman -Syu
Resolved for me as well !!


Linux is easy.. People are Difficult

Offline

#8 2015-03-30 18:10:57

Amunak
Member
From: Czech Republic
Registered: 2010-08-21
Posts: 15

Re: [SOLVED] Pacman refuses to upgrade due to missing key

For future self and possibly others: Check your system clock. I forgot that I removed the CMOS battery so my time reset to ~2002. The keys were obviously invalid at that time, which is why you get the error. I had to not only set the correct time but also reboot, then it worked.

(oh and it would be nice if pacstrap could just casually check time from some internet server and report if it is years off)

Last edited by Amunak (2015-03-30 18:11:47)

Offline

#9 2015-04-02 21:23:56

helix
Member
Registered: 2013-02-17
Posts: 173

Re: [SOLVED] Pacman refuses to upgrade due to missing key

I think the best solution for this case is

pacman -Sy archlinux-keyring
pacman -Su

Some people may say that the first command is a partial upgrade, but archlinux-keyring could be an exception especially considering that a full update follows right after. Why -Sy and not -S? To make sure you have the latest keys.

Offline

#10 2016-03-14 05:13:58

litchiware
Member
Registered: 2015-08-24
Posts: 2

Re: [SOLVED] Pacman refuses to upgrade due to missing key

helix wrote:

I think the best solution for this case is

pacman -Sy archlinux-keyring
pacman -Su

Some people may say that the first command is a partial upgrade, but archlinux-keyring could be an exception especially considering that a full update follows right after. Why -Sy and not -S? To make sure you have the latest keys.

Many thanks, you save my day

Offline

#11 2019-03-18 08:25:13

vikilyc
Member
Registered: 2019-03-18
Posts: 1

Re: [SOLVED] Pacman refuses to upgrade due to missing key

Need help,,,
I am seeing that some repository is truncated and and some key is missing
when I run  sudo pacman -Sy archlinux-keyring


warning: archlinux-keyring-20190123-2 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
error: could not open file /var/lib/pacman/local/x265-3.0-1/desc: No such file or directory

Packages (1) archlinux-keyring-20190123-2

Total Installed Size:  0.94 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring                     [######################] 100%
(1/1) checking package integrity                   [######################] 100%
(1/1) loading package files                        [######################] 100%
(1/1) checking for file conflicts                  [######################] 100%
(1/1) checking available disk space                [######################] 100%
:: Processing package changes...
(1/1) reinstalling archlinux-keyring               [######################] 100%
==> Appending keys from archlinux.gpg...
==> Locally signing trusted keys in keyring...
  -> Locally signing key D8AFDDA07A5B6EDFA7D8CCDAD6D055F927843F1C...
  -> Locally signing key DDB867B92AA789C165EEFA799B729B06A680C281...
  -> Locally signing key 684148BB25B49E986A4944C55184252D824B18E8...
  -> Locally signing key 91FFE0700E80619CEB73235CA88E23E377514E00...
  -> Locally signing key 0E8B644079F599DFC1DDC3973348882F6AC6A4C2...
  -> Locally signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7...
==> Importing owner trust values...
==> Disabling revoked keys in keyring...
  -> Disabling key 8F76BEEA0289F9E1D3E229C05F946DED983D4366...
  -> Disabling key 63F395DE2D6398BBE458F281F2DBB4931985A992...
  -> Disabling key 50F33E2E5B0C3D900424ABE89BDCF497A4BBCC7F...
  -> Disabling key 27FFC4769E19F096D41D9265A04F9397CDFD6BB0...
  -> Disabling key 39F880E50E49A4D11341E8F939E4F17F295AFBF4...
  -> Disabling key 8840BD07FC24CB7CE394A07CCF7037A4F27FB7DA...
  -> Disabling key 5559BC1A32B8F76B3FCCD9555FA5E5544F010D48...
  -> Disabling key 0B20CA1931F5DA3A70D0F8D2EA6836E1AB441196...
  -> Disabling key 07DFD3A0BC213FA12EDC217559B3122E2FA915EC...
  -> Disabling key 4FCF887689C41B09506BE8D5F3E1D5C5D30DB0AD...
  -> Disabling key 5A2257D19FF7E1E0E415968CE62F853100F0D0F0...
  -> Disabling key 7FA647CD89891DEDC060287BB9113D1ED21E1A55...
  -> Disabling key BC1FBE4D2826A0B51E47ED62E2539214C6C11350...
  -> Disabling key 4A8B17E20B88ACA61860009B5CED81B7C2E5C0D2...
  -> Disabling key 5696C003B0854206450C8E5BE613C09CB4440678...
  -> Disabling key 8CF934E339CAD8ABF342E822E711306E3C4F88BC...
  -> Disabling key F5A361A3A13554B85E57DDDAAF7EF7873CFD4BB6...
  -> Disabling key 5E7585ADFF106BFFBBA319DC654B877A0864983E...
  -> Disabling key 65EEFE022108E2B708CBFCF7F9E712E59AF5F22A...
  -> Disabling key 40440DC037C05620984379A6761FAD69BA06C6A9...
  -> Disabling key 34C5D94FE7E7913E86DC427E7FB1A3800C84C0A5...
  -> Disabling key 81D7F8241DB38BC759C80FCE3A726C6170E80477...
  -> Disabling key E7210A59715F6940CF9A4E36A001876699AD6E84...
  -> Disabling key 5357F3B111688D88C1D88119FCF2CB179205AC90...
  -> Disabling key FB871F0131FEA4FB5A9192B4C8880A6406361833...
  -> Disabling key 66BD74A036D522F51DD70A3C7F2A16726521E06D...
  -> Disabling key B1F2C889CB2CCB2ADA36D963097D629E437520BD...
  -> Disabling key 9515D8A8EAB88E49BB65EDBCE6B456CAF15447D5...
  -> Disabling key 40776A5221EF5AD468A4906D42A1DB15EC133BAD...
  -> Disabling key D4DE5ABDE2A7287644EAC7E36D1A9E70E19DAA50...
  -> Disabling key 44D4A033AC140143927397D47EFD567D4C7EA887...
==> Updating trust database...
gpg: next trustdb check due at 2019-06-02
ldconfig: file /usr/lib/libx265.so is truncated

ldconfig: file /usr/lib/libx265.so.169 is truncated

:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
arch4edu is up to date
archlinuxcn is up to date
:: Starting full system upgrade...
:: Replace xorg-mkfontdir with extra/xorg-mkfontscale? [Y/n] y
resolving dependencies...
error: could not open file /var/lib/pacman/local/x265-3.0-1/desc: No such file or directory
looking for conflicting packages...

Packages (192) appstream-glib-0.7.15-1  archlinux-appstream-data-20190226-1
               many packages......
Total Installed Size:  2016.36 MiB
Net Upgrade Size:        33.62 MiB

:: Proceed with installation? [Y/n] y
(191/191) checking keys in keyring                 [######################] 100%
downloading required keys...
error: key "7931B6D628C8D3BA" could not be looked up remotely
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.

Offline

#12 2019-03-18 08:48:19

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 8,929
Website

Re: [SOLVED] Pacman refuses to upgrade due to missing key


Sakura:-
Mobo: MSI X299 TOMAHAWK ARCTIC // Processor: Intel Core i7-7820X 3.6GHz // GFX: nVidia GeForce GTX 970 // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 5x 1TB HDD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

Board footer

Powered by FluxBB