How can I get rid of these NO_PUBKEY errors?












3














sudo apt-get update is giving me this error at the end. I'm using Y PPA Manager and it seems that now all PPAs are OK, but the problem (I think) is with the official Ubuntu repos:



W: GPG error: http://repository.spotify.com stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 13B00F1FD2C19886
W: GPG error: http://archive.ubuntu.com wily InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
W: GPG error: http://archive.canonical.com wily InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
W: GPG error: http://archive.ubuntu.com wily-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
W: GPG error: http://archive.ubuntu.com wily-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
W: GPG error: https://download.01.org vivid InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A902DDA375E52366
W: GPG error: http://archive.ubuntu.com wily-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
W: GPG error: http://archive.ubuntu.com wily-proposed InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32


Using Ubuntu 15.10



I've also tried this without success:



jose@jose-Lenovo-G400s:~$ sudo gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv 40976EAF437D05B5
gpg: requesting key 437D05B5 from hkp server keyserver.ubuntu.com
gpg: key 437D05B5: "Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1




jose@jose-Lenovo-G400s:~$ sudo gpg --export --armor 40976EAF437D05B5 | sudo apt-key add -
sudo: ignoring time stamp from the future
[sudo] password for jose:
gpg: keyblock resource `/etc/apt/trusted.gpg.d/webupd8team_ubuntu_y-ppa-manager.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/whatsapp-purple_ubuntu_ppa.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/wine_ubuntu_wine-builds.gpg': resource limit
jose@jose-Lenovo-G400s:~$


I don't know what I'm doing wrong. Thanks.










share|improve this question




















  • 4




    Possible duplicate of How do I fix the GPG error "NO_PUBKEY"?
    – Pilot6
    Mar 3 '16 at 19:46






  • 3




    Please run export LANG=C before posting command line outputs. Doing so will enforce english output until the end of the terminal session.
    – Jens Erat
    Mar 3 '16 at 20:24
















3














sudo apt-get update is giving me this error at the end. I'm using Y PPA Manager and it seems that now all PPAs are OK, but the problem (I think) is with the official Ubuntu repos:



W: GPG error: http://repository.spotify.com stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 13B00F1FD2C19886
W: GPG error: http://archive.ubuntu.com wily InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
W: GPG error: http://archive.canonical.com wily InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
W: GPG error: http://archive.ubuntu.com wily-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
W: GPG error: http://archive.ubuntu.com wily-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
W: GPG error: https://download.01.org vivid InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A902DDA375E52366
W: GPG error: http://archive.ubuntu.com wily-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
W: GPG error: http://archive.ubuntu.com wily-proposed InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32


Using Ubuntu 15.10



I've also tried this without success:



jose@jose-Lenovo-G400s:~$ sudo gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv 40976EAF437D05B5
gpg: requesting key 437D05B5 from hkp server keyserver.ubuntu.com
gpg: key 437D05B5: "Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1




jose@jose-Lenovo-G400s:~$ sudo gpg --export --armor 40976EAF437D05B5 | sudo apt-key add -
sudo: ignoring time stamp from the future
[sudo] password for jose:
gpg: keyblock resource `/etc/apt/trusted.gpg.d/webupd8team_ubuntu_y-ppa-manager.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/whatsapp-purple_ubuntu_ppa.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/wine_ubuntu_wine-builds.gpg': resource limit
jose@jose-Lenovo-G400s:~$


I don't know what I'm doing wrong. Thanks.










share|improve this question




















  • 4




    Possible duplicate of How do I fix the GPG error "NO_PUBKEY"?
    – Pilot6
    Mar 3 '16 at 19:46






  • 3




    Please run export LANG=C before posting command line outputs. Doing so will enforce english output until the end of the terminal session.
    – Jens Erat
    Mar 3 '16 at 20:24














3












3








3


2





sudo apt-get update is giving me this error at the end. I'm using Y PPA Manager and it seems that now all PPAs are OK, but the problem (I think) is with the official Ubuntu repos:



W: GPG error: http://repository.spotify.com stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 13B00F1FD2C19886
W: GPG error: http://archive.ubuntu.com wily InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
W: GPG error: http://archive.canonical.com wily InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
W: GPG error: http://archive.ubuntu.com wily-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
W: GPG error: http://archive.ubuntu.com wily-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
W: GPG error: https://download.01.org vivid InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A902DDA375E52366
W: GPG error: http://archive.ubuntu.com wily-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
W: GPG error: http://archive.ubuntu.com wily-proposed InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32


Using Ubuntu 15.10



I've also tried this without success:



jose@jose-Lenovo-G400s:~$ sudo gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv 40976EAF437D05B5
gpg: requesting key 437D05B5 from hkp server keyserver.ubuntu.com
gpg: key 437D05B5: "Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1




jose@jose-Lenovo-G400s:~$ sudo gpg --export --armor 40976EAF437D05B5 | sudo apt-key add -
sudo: ignoring time stamp from the future
[sudo] password for jose:
gpg: keyblock resource `/etc/apt/trusted.gpg.d/webupd8team_ubuntu_y-ppa-manager.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/whatsapp-purple_ubuntu_ppa.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/wine_ubuntu_wine-builds.gpg': resource limit
jose@jose-Lenovo-G400s:~$


I don't know what I'm doing wrong. Thanks.










share|improve this question















sudo apt-get update is giving me this error at the end. I'm using Y PPA Manager and it seems that now all PPAs are OK, but the problem (I think) is with the official Ubuntu repos:



W: GPG error: http://repository.spotify.com stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 13B00F1FD2C19886
W: GPG error: http://archive.ubuntu.com wily InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
W: GPG error: http://archive.canonical.com wily InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
W: GPG error: http://archive.ubuntu.com wily-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
W: GPG error: http://archive.ubuntu.com wily-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
W: GPG error: https://download.01.org vivid InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A902DDA375E52366
W: GPG error: http://archive.ubuntu.com wily-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
W: GPG error: http://archive.ubuntu.com wily-proposed InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32


Using Ubuntu 15.10



I've also tried this without success:



jose@jose-Lenovo-G400s:~$ sudo gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv 40976EAF437D05B5
gpg: requesting key 437D05B5 from hkp server keyserver.ubuntu.com
gpg: key 437D05B5: "Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1




jose@jose-Lenovo-G400s:~$ sudo gpg --export --armor 40976EAF437D05B5 | sudo apt-key add -
sudo: ignoring time stamp from the future
[sudo] password for jose:
gpg: keyblock resource `/etc/apt/trusted.gpg.d/webupd8team_ubuntu_y-ppa-manager.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/whatsapp-purple_ubuntu_ppa.gpg': resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/wine_ubuntu_wine-builds.gpg': resource limit
jose@jose-Lenovo-G400s:~$


I don't know what I'm doing wrong. Thanks.







apt updates repository gnupg






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 16 at 20:31









Zanna

50k13131238




50k13131238










asked Mar 3 '16 at 19:37









Jose Barakat

15314




15314








  • 4




    Possible duplicate of How do I fix the GPG error "NO_PUBKEY"?
    – Pilot6
    Mar 3 '16 at 19:46






  • 3




    Please run export LANG=C before posting command line outputs. Doing so will enforce english output until the end of the terminal session.
    – Jens Erat
    Mar 3 '16 at 20:24














  • 4




    Possible duplicate of How do I fix the GPG error "NO_PUBKEY"?
    – Pilot6
    Mar 3 '16 at 19:46






  • 3




    Please run export LANG=C before posting command line outputs. Doing so will enforce english output until the end of the terminal session.
    – Jens Erat
    Mar 3 '16 at 20:24








4




4




Possible duplicate of How do I fix the GPG error "NO_PUBKEY"?
– Pilot6
Mar 3 '16 at 19:46




Possible duplicate of How do I fix the GPG error "NO_PUBKEY"?
– Pilot6
Mar 3 '16 at 19:46




3




3




Please run export LANG=C before posting command line outputs. Doing so will enforce english output until the end of the terminal session.
– Jens Erat
Mar 3 '16 at 20:24




Please run export LANG=C before posting command line outputs. Doing so will enforce english output until the end of the terminal session.
– Jens Erat
Mar 3 '16 at 20:24










1 Answer
1






active

oldest

votes


















5














User mchid answered a similar question stating that:




apt can only handle 40 keys in /etc/apt/trusted.gpg.d . 41 keys and you will get the GPG error "no public key found" even if you go through all the steps to add the missing key(s).



Check to see if there are any unused keys in this file from ppa(s) you no longer use. If all are in use, consider removing some ppa(s) along with the corresponding keyfiles in /etc/apt/trusted.gpg.d




So I went to /etc/apt/trusted.gpg.d and deleted 2 GPG keys (now with 39 left in /etc/apt/trusted.gpg.d). sudo apt-get update worked OK and now I can upgrade any package.






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f741742%2fhow-can-i-get-rid-of-these-no-pubkey-errors%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    5














    User mchid answered a similar question stating that:




    apt can only handle 40 keys in /etc/apt/trusted.gpg.d . 41 keys and you will get the GPG error "no public key found" even if you go through all the steps to add the missing key(s).



    Check to see if there are any unused keys in this file from ppa(s) you no longer use. If all are in use, consider removing some ppa(s) along with the corresponding keyfiles in /etc/apt/trusted.gpg.d




    So I went to /etc/apt/trusted.gpg.d and deleted 2 GPG keys (now with 39 left in /etc/apt/trusted.gpg.d). sudo apt-get update worked OK and now I can upgrade any package.






    share|improve this answer




























      5














      User mchid answered a similar question stating that:




      apt can only handle 40 keys in /etc/apt/trusted.gpg.d . 41 keys and you will get the GPG error "no public key found" even if you go through all the steps to add the missing key(s).



      Check to see if there are any unused keys in this file from ppa(s) you no longer use. If all are in use, consider removing some ppa(s) along with the corresponding keyfiles in /etc/apt/trusted.gpg.d




      So I went to /etc/apt/trusted.gpg.d and deleted 2 GPG keys (now with 39 left in /etc/apt/trusted.gpg.d). sudo apt-get update worked OK and now I can upgrade any package.






      share|improve this answer


























        5












        5








        5






        User mchid answered a similar question stating that:




        apt can only handle 40 keys in /etc/apt/trusted.gpg.d . 41 keys and you will get the GPG error "no public key found" even if you go through all the steps to add the missing key(s).



        Check to see if there are any unused keys in this file from ppa(s) you no longer use. If all are in use, consider removing some ppa(s) along with the corresponding keyfiles in /etc/apt/trusted.gpg.d




        So I went to /etc/apt/trusted.gpg.d and deleted 2 GPG keys (now with 39 left in /etc/apt/trusted.gpg.d). sudo apt-get update worked OK and now I can upgrade any package.






        share|improve this answer














        User mchid answered a similar question stating that:




        apt can only handle 40 keys in /etc/apt/trusted.gpg.d . 41 keys and you will get the GPG error "no public key found" even if you go through all the steps to add the missing key(s).



        Check to see if there are any unused keys in this file from ppa(s) you no longer use. If all are in use, consider removing some ppa(s) along with the corresponding keyfiles in /etc/apt/trusted.gpg.d




        So I went to /etc/apt/trusted.gpg.d and deleted 2 GPG keys (now with 39 left in /etc/apt/trusted.gpg.d). sudo apt-get update worked OK and now I can upgrade any package.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Dec 16 at 20:32









        Zanna

        50k13131238




        50k13131238










        answered Mar 3 '16 at 21:43









        Jose Barakat

        15314




        15314






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f741742%2fhow-can-i-get-rid-of-these-no-pubkey-errors%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            數位音樂下載

            When can things happen in Etherscan, such as the picture below?

            格利澤436b