[SOLVED] error: key "A6234074498E9CEE" could not be looked up remotely

pdq · 2015-02-08 22:54:25

Ran into issue today trying to update my system, I searched forums for this specific problem to no avail.

sudo pacman -Syu
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (20) cmake-3.1.2-1  gparted-0.21.0-2  kdebase-dolphin-14.12.2-1
              kdebase-lib-14.12.2-1  kdebase-runtime-14.12.2-2
              kdegraphics-mobipocket-14.12.2-1  kdelibs-4.14.5-1
              kdemultimedia-ffmpegthumbs-14.12.2-1  kdepimlibs-4.14.5-1
              kdeutils-ark-14.12.2-1  libkcddb-14.12.2-1  linux-3.18.6-1
              linux-headers-3.18.6-1  livestreamer-1.11.1-2  nvidia-346.35-6
              oxygen-icons-14.12.2-1  packagekit-1.0.4-3  parted-3.2-2
              python2-pillow-2.7.0-1  udisks2-2.1.4-1

Total Installed Size:  291.11 MiB
Net Upgrade Size:       -0.43 MiB

:: Proceed with installation? [Y/n] y
(20/20) checking keys in keyring                   [----------------------] 100%
downloading required keys...
error: key "A6234074498E9CEE" 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.

Suggestions?

Last edited by pdq (2015-02-08 23:20:37)

frank604 · 2015-02-08 23:00:41

https://bbs.archlinux.org/viewtopic.php?id=191279
Does this help?

pdq · 2015-02-08 23:10:07

No luck with that.

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

Packages (1) archlinux-keyring-20141218-1

Total Installed Size:  0.62 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%
(1/1) reinstalling archlinux-keyring               [----------------------] 100%
==> Appending keys from archlinux.gpg...
==> Locally signing trusted keys in keyring...
  -> Locally signing key 0E8B644079F599DFC1DDC3973348882F6AC6A4C2...
  -> Locally signing key 684148BB25B49E986A4944C55184252D824B18E8...
  -> Locally signing key 44D4A033AC140143927397D47EFD567D4C7EA887...
  -> Locally signing key 27FFC4769E19F096D41D9265A04F9397CDFD6BB0...
  -> Locally signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7...
==> Importing owner trust values...
==> Disabling revoked keys in keyring...
  -> Disabling key F5A361A3A13554B85E57DDDAAF7EF7873CFD4BB6...
  -> Disabling key 7FA647CD89891DEDC060287BB9113D1ED21E1A55...
  -> Disabling key D4DE5ABDE2A7287644EAC7E36D1A9E70E19DAA50...
  -> Disabling key BC1FBE4D2826A0B51E47ED62E2539214C6C11350...
  -> Disabling key 9515D8A8EAB88E49BB65EDBCE6B456CAF15447D5...
  -> Disabling key 4A8B17E20B88ACA61860009B5CED81B7C2E5C0D2...
  -> Disabling key 63F395DE2D6398BBE458F281F2DBB4931985A992...
  -> Disabling key 0B20CA1931F5DA3A70D0F8D2EA6836E1AB441196...
  -> Disabling key 8F76BEEA0289F9E1D3E229C05F946DED983D4366...
  -> Disabling key 66BD74A036D522F51DD70A3C7F2A16726521E06D...
  -> Disabling key 81D7F8241DB38BC759C80FCE3A726C6170E80477...
  -> Disabling key E7210A59715F6940CF9A4E36A001876699AD6E84...
==> Updating trust database...
gpg: next trustdb check due at 2016-01-22
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (20) cmake-3.1.2-1  gparted-0.21.0-2  kdebase-dolphin-14.12.2-1
              kdebase-lib-14.12.2-1  kdebase-runtime-14.12.2-2
              kdegraphics-mobipocket-14.12.2-1  kdelibs-4.14.5-1
              kdemultimedia-ffmpegthumbs-14.12.2-1  kdepimlibs-4.14.5-1
              kdeutils-ark-14.12.2-1  libkcddb-14.12.2-1  linux-3.18.6-1
              linux-headers-3.18.6-1  livestreamer-1.11.1-2  nvidia-346.35-6
              oxygen-icons-14.12.2-1  packagekit-1.0.4-3  parted-3.2-2
              python2-pillow-2.7.0-1  udisks2-2.1.4-1

Total Installed Size:  291.11 MiB
Net Upgrade Size:       -0.43 MiB

:: Proceed with installation? [Y/n] y
(20/20) checking keys in keyring                   [----------------------] 100%
downloading required keys...
error: key "A6234074498E9CEE" 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.

frank604 · 2015-02-08 23:13:39

Did you follow the rest of the thread and try https://wiki.archlinux.org/index.php/Pa … mport_keys

pdq · 2015-02-08 23:19:47

Thanks frank604, I got it to work on the 3rd server attempt.

#keyserver hkp://pool.sks-keyservers.net
#keyserver hkp://pgp.mit.edu:11371
keyserver hkp://keyserver.kjsl.com:80 <-- finally worked

My issue is solved! I missed that part in the wiki, thanks again.

Last edited by pdq (2015-02-08 23:26:33)

frank604 · 2015-02-08 23:26:28

Cool stuff. happy Syu'n away

ElectricPrism · 2015-02-09 02:32:57

/etc/pacman.d/gnupg/gpg.conf

keyserver hkp://keyserver.kjsl.com:80

didn't work for me

EDIT:

Here's what fixed the problem for me:

# Archive the GNUPG directories
mv $HOME/.gnupg $HOME/.gnupg.bak
sudo mv /root/.gnupg /root/.gnupg.bak

# This one fixed the GNUPG Error
dirmngr </dev/null

# Refresh Keys
pacman-key --init
pacman-key --populate archlinux
pacman-key --refresh-keys

Last edited by ElectricPrism (2015-02-09 02:44:29)

McMuntjac · 2015-02-09 23:59:29

ElectricPrism wrote:

...

# Archive the GNUPG directories
mv $HOME/.gnupg $HOME/.gnupg.bak
>sudo mv /etc/pacman.d/gnupg /etc/pacman.d/gnupg.bak 
...

it was "mv /etc/pacman.d/gnupg /etc/pacman.d/gnupg.bak" rather than the same at ".../root/.gnupg..." that actually did something for me and allowed dirmngr to work, not sure if I'm being obvious. I should be, given that is what is written in the wiki (which needs a different password from the forum for the same profile as the forum?).

Last edited by McMuntjac (2015-02-10 00:04:26)

KatsumeBlisk · 2015-02-10 12:06:12

I'm still having this issue. I've tried switching keyservers and rebuilding the keyring. I'm not updating but installing packagekit on a new system. I see that you were upgrading that package and that the key that was having the issue is the same string. Any help? packagekit isn't required for my system, but it makes it easier to use.

artem.jackson · 2015-02-10 14:10:29

Have the same problem.
But nothing helps.

mauritiusdadd · 2015-02-10 15:32:47

Hi, I had the same problem and there is also a bug report here: https://bugs.archlinux.org/task/43759

For me the following procedure worked (as root):

# rm -R /etc/pacman.d/gnupg/
# rm -R /root/.gnupg/  # only if the directory exists
# gpg --refresh-keys
# pacman-key --init && pacman-key --populate
# pacman-key --refresh-keys

--EDIT--

Note that since this procedure resets your pacman keyring, you have to add again any custom key

Last edited by mauritiusdadd (2015-02-20 05:55:13)

poki2 · 2015-02-11 14:07:04

mauritiusdadd wrote:

Hi, I had the same problem and there is also a bug report here: https://bugs.archlinux.org/task/43759
For me the following procedure worked (as root):
# rm -R /etc/pacman.d/gnupg/
# rm -R /root/.gnupg/  # only if the directory exists
# gpg --refresh-keys
# pacman-key --init && pacman-key --populate
# pacman-key --refresh-keys

This worked perfectly fine for me. Thanks.

despian · 2015-02-12 09:28:47

mauritiusdadd wrote:

Hi, I had the same problem and there is also a bug report here: https://bugs.archlinux.org/task/43759
For me the following procedure worked (as root):
# rm -R /etc/pacman.d/gnupg/
# rm -R /root/.gnupg/  # only if the directory exists
# gpg --refresh-keys
# pacman-key --init && pacman-key --populate
# pacman-key --refresh-keys

+1 worked for me too.

dharmaslacker · 2015-03-06 06:37:03

I simply used the advice at https://bbs.archlinux.org/, namely:

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

That worked for me.

mattz · 2015-05-26 05:56:49

Had the same problem during initial install. Noticed that date was set to Jan 1 2000. As a result, keys were future-dated. No more problems after setting the date/time correctly.

theking2 · 2017-11-17 20:27:50

Hi there.

Have a similar problem but at pacman-key --refresh-keys I get:

gpg: refreshing 94 keys from hkp://pool.sks-keyservers.net
gpg: keyserver refresh failed: Invalid argument
==> ERROR: A specified local key could not be updated from a keyserver.

WorMzy · 2017-11-17 20:55:29

You really don't learn, do you? Even after eight years, and repeated reminders, you still choose to ignore our rules. Enough is enough.

Closing, binning, banning.

Arch Linux

#1 2015-02-08 22:54:25

[SOLVED] error: key "A6234074498E9CEE" could not be looked up remotely

#2 2015-02-08 23:00:41

Re: [SOLVED] error: key "A6234074498E9CEE" could not be looked up remotely

#3 2015-02-08 23:10:07

Re: [SOLVED] error: key "A6234074498E9CEE" could not be looked up remotely

#4 2015-02-08 23:13:39

Re: [SOLVED] error: key "A6234074498E9CEE" could not be looked up remotely

#5 2015-02-08 23:19:47

Re: [SOLVED] error: key "A6234074498E9CEE" could not be looked up remotely

#6 2015-02-08 23:26:28

Re: [SOLVED] error: key "A6234074498E9CEE" could not be looked up remotely

#7 2015-02-09 02:32:57

Re: [SOLVED] error: key "A6234074498E9CEE" could not be looked up remotely

#8 2015-02-09 23:59:29

Re: [SOLVED] error: key "A6234074498E9CEE" could not be looked up remotely

#9 2015-02-10 12:06:12

Re: [SOLVED] error: key "A6234074498E9CEE" could not be looked up remotely

#10 2015-02-10 14:10:29

Re: [SOLVED] error: key "A6234074498E9CEE" could not be looked up remotely

#11 2015-02-10 15:32:47

Re: [SOLVED] error: key "A6234074498E9CEE" could not be looked up remotely

#12 2015-02-11 14:07:04

Re: [SOLVED] error: key "A6234074498E9CEE" could not be looked up remotely

#13 2015-02-12 09:28:47

Re: [SOLVED] error: key "A6234074498E9CEE" could not be looked up remotely

#14 2015-03-06 06:37:03

Re: [SOLVED] error: key "A6234074498E9CEE" could not be looked up remotely

#15 2015-05-26 05:56:49

Re: [SOLVED] error: key "A6234074498E9CEE" could not be looked up remotely

#16 2017-11-17 20:27:50

Re: [SOLVED] error: key "A6234074498E9CEE" could not be looked up remotely

#17 2017-11-17 20:55:29

Re: [SOLVED] error: key "A6234074498E9CEE" could not be looked up remotely

Board footer