ICS/Lotus (mostly), Linux, Travel, Skiing, Mixology, and Random Musing of Interest

Fixing Public Key Repository Errors on Ubuntu

Bill Malchisky  September 2 2014 12:01:00 AM
Most of have seen at one point of another a error when updating packages, stemming from an untrusted repository.

W: GPG error:
http://security.ubuntu.com precise-security Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5

Here is one fix that works reliably well. Perhaps it will save you some time.

1. Syntax: sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys
2. $ sudo apt-get update

Repeat for each instance of the same received error after the update command in number two above. For this example, I received two NO_PUBKEY errors, one of which is listed above.

malchw@san-domino:~$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 40976EAF437D05B5

Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /tmp/tmp.rFoBoQHFbu --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver keyserver.ubuntu.com --recv-keys 40976EAF437D05B5

gpg: requesting key 437D05B5 from hkp server keyserver.ubuntu.com

gpg: key 437D05B5: public key "Ubuntu Archive Automatic Signing Key " imported

gpg: no ultimately trusted keys found

gpg: Total number processed: 1

gpg:               imported: 1


malchw@san-domino:~$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys B22A95F88110A93A
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /tmp/tmp.xHZdcG77tR --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver keyserver.ubuntu.com --recv-keys B22A95F88110A93A

gpg: requesting key 8110A93A from hkp server keyserver.ubuntu.com

gpg: key 8110A93A: public key "Launchpad PPA for Bumlebee Project" imported

gpg: Total number processed: 1

gpg:               imported: 1  (RSA: 1)


Run step two above, which came back clean. All done. Nice and easy.



Comments
No Comments Found

Powered by IBM Lotus Domino 8 | Lotus User Group | Get Firefox! | This blog is listed on Planet Lotus   IBM Certified

© 2010 William Malchisky.