When checking update got following


""[GPG error: http://packages.medibuntu.org hardy Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2EBC26B60C5A2783
GPG error: http://ppa.launchpad.net hardy Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A6DCF7707EBC211F
Failed to fetch http://archive.getdeb.net/ubuntu/dis...86/Packages.gz 404 Not Found
Failed to fetch http://ppa.launchpad.net/kubuntu-ppa...86/Packages.gz 404 Not Found
Failed to fetch http://ppa.launchpad.net/kubuntu-ppa...86/Packages.gz 404 Not Found
Failed to fetch http://ppa.launchpad.net/ubuntu-mozi...86/Packages.gz 404 Not Found
Failed to fetch http://ppa.launchpad.net/ubuntu-mozi...86/Packages.gz 404 Not Found
Failed to fetch http://ppa.launchpad.net/ubuntu-mozi...86/Packages.gz 404 Not Found
Some index files failed to download, they have been ignored, or old ones used instead.]

How significant is this & how do I correct?? :: if necessary[SIZE="3"][/SIZE

Ron:

Medibuntu is an 'accessory' repository for additional packages that are not part of the regular Ubuntu install. For the most part, it gives you additional media packages (MEDIbuntu) that are not open source. The fact that the GPG key is missing is not a big issue. It just means that you failed to list the GPG key when you added medibuntu to your list of repositories. The GPG key is a security feature that ensures that you are indeed receiving bona fide packages from Medibuntu.

The other issues I am not sure of. It may be that medibuntu is being updated, and the packages you want are temporarily not available. It may also mean that Medibuntu is moving on, and the packages for your version of Ubuntu are no longer available.

I've come across similar errors myself, using Kubuntu 8.04, which is getting a bit old. You don't mention what version of Ubuntu that you are using, but I assume that it is 8.04 from the error information listing it as a 'hardy' update.

Perhaps someone more knowledgeable than I can answer the rest of your questions.

Frank.

To remedy the public key errors you need to go to the site hosting them and download the key and add it to your keys.

As for the other errors it could be that the server is down or it is a broken link, check to make sure the repository links are entered correctly in your source.list.