NO_PUBKEY 2EBC26B60C5A2783

Bug #711615 reported by Lewis Skinner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Medibuntu
Invalid
Undecided
Unassigned

Bug Description

Hi guys.

I've been running Ubuntu for some time now, and I usually perform a clean install everytime.

This time however, following installation of Maverick, I tried to add medibuntu as on these instructions:
https://help.ubuntu.com/community/Medibuntu

And, following the first command, I get terminal output as follows:

W: GPG error: http://packages.medibuntu.org maverick Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2EBC26B60C5A2783
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/maverick-security/Release.gpg Something wicked happened resolving 'security.ubuntu.com:http' (-5 - No address associated with hostname)

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

This is causing issues with my downloading medibuntu packages. Can anyone help?

Tags: key pubkey public
Revision history for this message
Gauvain Pocentek (gpocentek) wrote :

Hi,

Make sure that the medibuntu-keyring package is installed. If not, install and run 'apt-get update', the gpg warning should disappear.
Anyway this shouldn't prevent packages installation.

Changed in medibuntu:
status: New → Incomplete
Revision history for this message
Lewis Skinner (lewisskinner) wrote :

It is. I've followed all instructions on the medibuntu page shown above.

I've had similar problems with other repos (below), even straight out of the box (I installed from scratch, formatting /home partition as well).

----
Fetched 396B in 10s (36B/s)
W: Failed to fetch http://extras.ubuntu.com/ubuntu/dists/maverick/Release.gpg Something wicked happened resolving 'extras.ubuntu.com:http' (-5 - No address associated with hostname)

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

That's my other error. I've had to comment out that repo in sources.list

Revision history for this message
Lewis Skinner (lewisskinner) wrote :

OK, double-checking, I did everything I ought to as per the instructions, however, it is STILL telling me that there is no public key available.

W: GPG error: http://packages.medibuntu.org maverick Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2EBC26B60C5A2783
W: Failed to fetch http://archive.canonical.com/ubuntu/dists/maverick/Release.gpg Something wicked happened resolving 'archive.canonical.com:http' (-5 - No address associated with hostname)

W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/maverick-security/Release.gpg Something wicked happened resolving 'security.ubuntu.com:http' (-5 - No address associated with hostname)

W: Failed to fetch http://deb.torproject.org/torproject.org/dists/maverick/Release.gpg Something wicked happened resolving 'deb.torproject.org:http' (-5 - No address associated with hostname)

W: Failed to fetch http://ppa.launchpad.net/team-xbmc/ppa/ubuntu/dists/maverick/Release.gpg Something wicked happened resolving 'ppa.launchpad.net:http' (-5 - No address associated with hostname)

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

However, checking system -> administration -> software sources, 'authentication' tab, there's no medibuntu key. How can I add this?

Revision history for this message
Gauvain Pocentek (gpocentek) wrote :

Could you reinstall the medibuntu-keyring package using a GUI or the following command:
sudo apt-get install --reinstall medibuntu-keyring

This seemed to work for the reporter of bug #656164

Thanks

Changed in medibuntu:
status: Incomplete → Triaged
Revision history for this message
Lewis Skinner (lewisskinner) wrote :

Not to worry - I've solved it!

It was a DNS error caused by resolv.conf and my router. Once I manually entered a DNS and write-protected it, I was fine

Changed in medibuntu:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.