Ubuntu

synaptic W: GPG error: http://ppa.launchpad.net intrepid Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DAA9427DCBF475C3

Asked by David Oxland on 2009-02-15

Binary package hint: synaptic

W: GPG error: http://ppa.launchpad.net intrepid Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DAA9427DCBF475C3

Attempting a reload of Synaptic and also this has happened when using update manager
expected a succesful reload
The above error was presented

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/sbin/synaptic
NonfreeKernelModules: nvidia
Package: synaptic 0.62.1ubuntu10
ProcAttrCurrent: unconfined
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: synaptic
Uname: Linux 2.6.27-11-generic i686

David Oxland (doxland) said : #1
Chris Coulson (chrisccoulson) said : #2

Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We appreciate the difficulties you are facing, but it would make more sense to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs#When%20not%20to%20file%20a%20bug.

Chris Coulson (chrisccoulson) said : #3

Please follow the instructions here for adding the keys for the PPA's that you are using:

https://help.launchpad.net/Packaging/PPA#Adding%20a%20PPA%20to%20your%20Ubuntu%20repositories

Fabián Rodríguez (magicfab) said : #4

Fabián Rodríguez suggests this article as an answer to your question:
FAQ #358: “Synaptic produces a W: GPG error: http://ppa.launchpad.net intrepid Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DAA9427DCBF475C3”.

Fabián Rodríguez (magicfab) said : #5

Fabián Rodríguez suggests this article as an answer to your question:
FAQ #359: “Synaptic produces a GPG error: “signatures couldn't be verified because the public key is not available”. How to add missing PPA public keys ?”.

Dushyant (juneja-dushyant) said : #6

Hey! I tried as directed by the article FAQ#359, but the following error came out at the terminal:

I wrote:
sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 6AF0E1940624A220

Terminal output was:
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --recv-keys --keyserver keyserver.ubuntu.com 6AF0E1940624A220
gpg: requesting key 0624A220 from hkp server keyserver.ubuntu.com
gpgkeys: HTTP fetch error 7: couldn't connect to host
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0

This is strange when I'm able to update my system behind a proxy using the GUI as sudo apt-get update

Please tell me how to overcome this problem.

Can you help with this problem?

Provide an answer of your own, or ask David Oxland for more information if necessary.

To post a message you must log in.