It's FOSS

A Linux and Open Source Web Portal

You are here: Home / Tutorial / [Solved] W: GPG error: The following signatures couldn’t be verified in Ubuntu

[Solved] W: GPG error: The following signatures couldn’t be verified in Ubuntu

Last updated By 11 Comments

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

W GPG Error The following signatures couldn't be verified because the public key is not available:

It is quite evident from the error message itself that the said public key was not found in the system. 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 68980A0EA10B4DE8

This 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:

3 Shares

  • I do as per given Instruction but still Issue is their…. please suggest.

    $ sudo apt-key adv –keyserver keyserver.ubuntu.com –recv-keys 68980A0EA10B4DE8
    [sudo] password for tbl:
    Executing: /tmp/apt-key-gpghome.38xWjEz82H/gpg.1.sh –keyserver keyserver.ubuntu.com –recv-keys 68980A0EA10B4DE8
    gpg: key 68980A0EA10B4DE8: “Stefano Karapetsas (MATE) ” not changed
    gpg: Total number processed: 1
    gpg: unchanged: 1
    [email protected]:~$ sudo apt-get update

    $ sudo apt-get update
    Hit:1 http://in.archive.ubuntu.com/ubuntu bionic InRelease
    Hit:2 http://in.archive.ubuntu.com/ubuntu bionic-updates InRelease
    Hit:3 http://in.archive.ubuntu.com/ubuntu bionic-backports InRelease
    Hit:4 http://ppa.launchpad.net/linuxuprising/java/ubuntu bionic InRelease
    Hit:5 http://ppa.launchpad.net/webupd8team/java/ubuntu precise InRelease
    Hit:6 http://ppa.launchpad.net/webupd8team/java/ubuntu bionic InRelease
    Get:7 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
    Get:8 https://apt.dockerproject.org/repo ubuntu-xenial InRelease [48.7 kB]
    Err:8 https://apt.dockerproject.org/repo ubuntu-xenial InRelease
    The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY F76221572C52609D
    Reading package lists… Done
    W: GPG error: https://apt.dockerproject.org/repo ubuntu-xenial InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY F76221572C52609D
    E: The repository ‘https://apt.dockerproject.org/repo ubuntu-xenial 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.

    Reply
    • >
    Copy link
    CopyCopied