EasyPeasy Overview

Missing missing repository GPG keys

Bug #344806 reported by Jon Ramvi on 2009-03-18

This bug affects 5 people

Affects		Status	Importance	Assigned to	Milestone
	EasyPeasy Overview	Confirmed	Critical	Jon Ramvi	EasyPeasy Overview 1.6
	1.5	New	Undecided	Unassigned

Bug Description

Repositories are missing GPG keys which returns warnings to the user

"i got this error after adding the repo's:

W: GPG-fout: http://ppa.launchpad.net intrepid Release: De volgende ondertekeningen konden niet geverifieerd worden omdat de publieke sleutel niet beschikbaar is: NO_PUBKEY 60D11217247D1CFF
W: GPG-fout: http://ppa.launchpad.net intrepid Release: De volgende ondertekeningen konden niet geverifieerd worden omdat de publieke sleutel niet beschikbaar is: NO_PUBKEY 3F2A5EE4B796B6FE
W: GPG-fout: http://www.array.org intrepid Release: De volgende ondertekeningen konden niet geverifieerd worden omdat de publieke sleutel niet beschikbaar is: NO_PUBKEY 9B25830FFD0C2C24

its in dutch, but,

i googled around and found this gentoo weblog and (probably) found an answer,

[quote]
if you come across this error after running aptitude update

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 7D2C7A23BF810CD5
W: You may want to run apt-get update to correct these problems

due to a missing GPG key do the following to correct the problem

gpg --keyserver subkeys.pgp.net --recv 7D2C7A23BF810CD5

Replace the key number “7D2C7A23BF810CD5″ with the one included in your error message

gpg --export --armor 7D2C7A23BF810CD5 | sudo apt-key add -

After that, the key will be added to a list and the error will not reappear.

apt-get update
[/quote]

seems to work for me!
can anyone check it?"

Jon Ramvi (ramvi) on 2009-03-18

Changed in easypeasy:
assignee:	nobody → ramvi
importance:	Undecided → Medium
milestone:	none → 2.0beta
status:	New → Confirmed

Revision history for this message

christianedward (christian-christianedwards) wrote on 2009-08-11:

Screenshot-Untitled Window.png Edit (59.4 KiB, image/png)

I have the same problem on the Acer Aspire One EP1.5 but after trying your solution I end up with the following error.
W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used.GPG error: http://gb.archive.ubuntu.com jaunty Release: The following signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key <email address hidden>

W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used.GPG error: http://ppa.launchpad.net jaunty Release: The following signatures were invalid: BADSIG 60D11217247D1CFF Launchpad PPA for OpenOffice.org Scribblers

W: Failed to fetch http://gb.archive.ubuntu.com/ubuntu/dists/jaunty/Release

W: Failed to fetch http://ppa.launchpad.net/openoffice-pkgs/ppa/ubuntu/dists/jaunty/Release

W: Failed to fetch http://ppa.launchpad.net/ubuntu-x-swat/x-updates/ubuntu/dists/jaunty/Release

W: Some index files failed to download, they have been ignored, or old ones used instead.

Revision history for this message

christianedward (christian-christianedwards) wrote on 2009-08-27:

Found this
http://en.newinstance.it/2009/06/22/the-following-signatures-were-invalid-badsig-40976eaf437d05b5-ubuntu-archive-automatic-signing-key/
Which suggest you do this:
#apt-get clean
#cd /var/lib/apt
#mv lists lists.old
#mkdir -p lists/partial
#apt-get clean
#apt-get update
This sorted it for me.

Revision history for this message

Jean Roberto Souza (sjeanr) wrote on 2009-09-19:

Yes

the instructions by christianedward solved the problem on my eee 900 easypeasy 1.5

Thank you! :)

Revision history for this message

Ptericles (spamn8me-registration) wrote on 2009-09-19:

This worked for me too! Thanks so much. (I just installed easy peasy 1.5)
I copied this soln to the easypeasy forum post on this topic.

Revision history for this message

jeepGuy (tom-bearpaws) wrote on 2009-09-19:

Me too - thanks!

Revision history for this message

Geoffrey Allan Plauche (veritasnoctis) wrote on 2009-09-24:

I'm not sure how this is related to the Firefox 3.0/3.5 mplayer plugin bug I reported? I don't get any warnings about missing repository gpg keys. The problem I have is that when I try to install the mplayer plugin via Synaptic, it wants to install Firefox 3.0 and branding. Maybe the mplayer plugin is not updated to work with 3.5 yet? Or maybe it's a different issue? I don't know.

Revision history for this message

Jon Ramvi (ramvi) wrote on 2009-09-24:

Oh, I understand now. I'll change it back