Ubuntu and update errors are inseparable. Every now and then I encounter errors while updating the system after adding a new source. The other day I was trying to install Mate desktop environment when I got this GPG error while updating the system:
W: GPG error: http://repo.mate-desktop.org saucy InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 68980A0EA10B4DE8
It is quite evident from the error message itself that the said public key was not found in the system. What happens here is that you had added some third-party repository. Every such software has a signature mechanism so that your system know that you are downloading that particular software from the repository you had added.
If the developer changes his/her public key and then provides an update, your system raises an alarm that the public key it know is not found anymore.
In this quick post I’ll show you how to fix this W: GPG error: The following signatures couldn’t be verified because the public key is not available: NO error.
Fix GPG error: The following signatures couldn’t be verified
What we need to do is to fetch this public key in the system. Get the key number from the message. In the above message, the key is 68980A0EA10B4DE8. Now use that key in the following command:
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 68980A0EA10B4DE8This will add the key to the system. Just do an sudo apt-get update and you should not see this error any more. I hope this solved the problem for you.
As I said, Ubuntu and update errors are inseparable. Here are some of the most common Ubuntu update errors:
- The following signatures were invalid: BADSIG
- Problem with MergeList
- Partial upgrade error
- Failed to download repository information. Check your internet connection.
Let me know in the comments if this quick tip helped you fix this error or not.
Thank you, it works!
Regards from Germany
You are welcome. Eddy.
I am not to resolve issue in ubuntu18 for no pub key for docker installation. Please suggest
Thanks Abhishek. This perfectly worked.
Glad to hear that, Saikat.
W: GPG error: http://extras.ubuntu.com/ubuntu precise Release: The following signatures were invalid: C47415DFF48C09645B78609416126D3A3E5C1192
E: The repository ‘http://extras.ubuntu.com/ubuntu precise Release’ is not signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/4.0 Release: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 68818C72E52529D4
E: The repository ‘http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/4.0 Release’ is not signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://archive.canonical.com/ubuntu precise Release: The following signatures were invalid: 630239CC130E1A7FD81A27B140976EAF437D05B5
E: The repository ‘http://archive.canonical.com/ubuntu precise Release’ is not signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://us.archive.ubuntu.com/ubuntu precise-security InRelease: The following signatures were invalid: 630239CC130E1A7FD81A27B140976EAF437D05B5
E: The repository ‘http://us.archive.ubuntu.com/ubuntu precise-security InRelease’ is not signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://us.archive.ubuntu.com/ubuntu precise-updates InRelease: The following signatures were invalid: 630239CC130E1A7FD81A27B140976EAF437D05B5
E: The repository ‘http://us.archive.ubuntu.com/ubuntu precise-updates InRelease’ is not signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://us.archive.ubuntu.com/ubuntu precise-backports InRelease: The following signatures were invalid: 630239CC130E1A7FD81A27B140976EAF437D05B5
E: The repository ‘http://us.archive.ubuntu.com/ubuntu precise-backports InRelease’ is not signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://us.archive.ubuntu.com/ubuntu precise Release: The following signatures were invalid: 630239CC130E1A7FD81A27B140976EAF437D05B5
E: The repository ‘http://us.archive.ubuntu.com/ubuntu precise Release’ is not signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Sir, I am getting these kind of error How can i resolve it properly? Can you please help me with it thanks in advance.
You are using Ubuntu 12.04 which has reached its end of life in 2017.
You need to take a backup of your data on an external disk and then install a newer version of Ubuntu like 18.04 or 20.04 (stable release coming end of April).
Thanks