Page 1 of 5 123 ... LastLast
Results 1 to 10 of 42

Thread: HOWTO: Fix GPG errors for bad/deleted keys

  1. #1
    Join Date
    Mar 2006
    Location
    Canada
    Beans
    1,313
    Distro
    Ubuntu 10.10 Maverick Meerkat

    HOWTO: Fix GPG errors for bad/deleted keys

    I don't know what I did, but one day I started using Ubuntu and all my public signature keys for downloading software were all deleted.

    This error popped up after running "System > Administration > Update Manager"
    W: GPG error: http://archive.canonical.com jaunty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5
    W: GPG error: http://download.virtualbox.org jaunty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DCF9F87B6DFBCBAE
    W: GPG error: http://packages.medibuntu.org jaunty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2EBC26B60C5A2783
    W: GPG error: http://archive.ubuntu.com jaunty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5
    W: GPG error: http://archive.ubuntu.com jaunty-updates Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5
    W: GPG error: http://archive.getdeb.net jaunty-getdeb-testing Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A8A515F046D7E7CF
    W: GPG error: http://archive.ubuntu.com jaunty-security Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5
    W: GPG error: http://ppa.launchpad.net jaunty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6E871C4A881574DE
    W: GPG error: http://ppa.launchpad.net jaunty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 28A8205077558DD0
    W: GPG error: http://ppa.launchpad.net jaunty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D739676F7613768D
    W: GPG error: http://ppa.launchpad.net jaunty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8C851674F96FD737
    W: GPG error: http://ppa.launchpad.net jaunty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C0B56813051D8B58
    W: GPG error: http://ppa.launchpad.net jaunty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 4874D3686E80C6B7
    W: GPG error: http://ppa.launchpad.net jaunty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 60D11217247D1CFF
    W: GPG error: http://archive.ubuntu.com jaunty-backports Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5
    W: GPG error: http://ppa.launchpad.net jaunty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5A9A06AEF9CB8DB0
    W: GPG error: http://ppa.launchpad.net jaunty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6D975C4791E7EE5E
    W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used.GPG error: http://ppa.launchpad.net jaunty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5A9BF3BB4E5E17B5

    W: GPG error: http://ppa.launchpad.net jaunty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7FB8BEE0A1F196A8
    W: Failed to fetch http://ppa.launchpad.net/chromium-da...jaunty/Release

    W: Some index files failed to download, they have been ignored, or old ones used instead.
    The fix for this is to re-download the keys using the hexidecimal numbers given in the error (I bolded them above).

    NOTE: Your hexadecimal numbers may be different then mine, so make sure to use the hexadecimals numbers in your error, not mine.

    Type this command into the terminal ("Applications > Accessories > Terminal")
    Code:
    sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys
    And then add the hexadecimal numbers to the command (again, these are my keys from my error. Make sure to use your own):
    sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 40976EAF437D05B5 DCF9F87B6DFBCBAE 2EBC26B60C5A2783 A8A515F046D7E7CF 6E871C4A881574DE 28A8205077558DD0 D739676F7613768D 8C851674F96FD737 C0B56813051D8B58 4874D3686E80C6B7 60D11217247D1CFF 5A9A06AEF9CB8DB0 6D975C4791E7EE5E 5A9BF3BB4E5E17B5 7FB8BEE0A1F196A8
    The output should look like this:
    gpg: requesting key 437D05B5 from hkp server keyserver.ubuntu.com
    gpg: requesting key 6DFBCBAE from hkp server keyserver.ubuntu.com
    gpg: requesting key 0C5A2783 from hkp server keyserver.ubuntu.com
    gpg: requesting key 46D7E7CF from hkp server keyserver.ubuntu.com
    gpg: requesting key 881574DE from hkp server keyserver.ubuntu.com
    gpg: requesting key 77558DD0 from hkp server keyserver.ubuntu.com
    gpg: requesting key 7613768D from hkp server keyserver.ubuntu.com
    gpg: requesting key F96FD737 from hkp server keyserver.ubuntu.com
    gpg: requesting key 051D8B58 from hkp server keyserver.ubuntu.com
    gpg: requesting key 6E80C6B7 from hkp server keyserver.ubuntu.com
    gpg: requesting key 247D1CFF from hkp server keyserver.ubuntu.com
    gpg: requesting key F9CB8DB0 from hkp server keyserver.ubuntu.com
    gpg: requesting key 91E7EE5E from hkp server keyserver.ubuntu.com
    gpg: requesting key 4E5E17B5 from hkp server keyserver.ubuntu.com
    gpg: requesting key A1F196A8 from hkp server keyserver.ubuntu.com
    gpg: key 437D05B5: "Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>" not changed
    gpg: key 6DFBCBAE: public key "Sun Microsystems, Inc. (xVM VirtualBox archive signing key) <info@virtualbox.org>" imported
    gpg: key 0C5A2783: public key "Medibuntu Packaging Team <admin@lists.medibuntu.org>" imported
    gpg: key 46D7E7CF: public key "GetDeb Archive Automatic Signing Key <archive@getdeb.net>" imported
    gpg: key 881574DE: public key "Launchpad PPA for Bisigi" imported
    gpg: key 77558DD0: public key "Launchpad PPA for GNOME Do Core Team" imported
    gpg: key 7613768D: public key "Launchpad PPA named vlc for Christoph Korn" imported
    gpg: key F96FD737: public key "Launchpad PPA for Paul Gevers" imported
    gpg: key 051D8B58: public key "Launchpad PPA for GStreamer developers" imported
    gpg: key 6E80C6B7: public key "Launchpad PPA for Banshee Team" imported
    gpg: key 247D1CFF: public key "Launchpad PPA for OpenOffice.org Scribblers" imported
    gpg: key F9CB8DB0: public key "Launchpad PPA for Ubuntu Wine Team" imported
    gpg: key 91E7EE5E: public key "Launchpad PPA for XBMC for Linux" imported
    gpg: key 4E5E17B5: public key "Launchpad PPA for chromium-daily" imported
    gpg: key A1F196A8: public key "Launchpad PPA for Pidgin Developers" imported
    gpg: no ultimately trusted keys found
    gpg: Total number processed: 15
    gpg: imported: 14 (RSA: 12)
    gpg: unchanged: 1
    Then you should have no more errors!

  2. #2
    Join Date
    Feb 2007
    Beans
    766
    Distro
    Ubuntu Development Release

    Re: HOWTO: Fix GPG errors for bad/deleted keys

    Quote Originally Posted by altonbr View Post
    I don't know what I did, but one day I started using Ubuntu and all my public signature keys for downloading software were all deleted.

    This error popped up after running "System > Administration > Update Manager"


    The fix for this is to re-download the keys using the hexidecimal numbers given in the error (I bolded them above).

    NOTE: Your hexadecimal numbers may be different then mine, so make sure to use the hexadecimals numbers in your error, not mine.

    Type this command into the terminal ("Applications > Accessories > Terminal")
    Code:
    sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys
    And then add the hexadecimal numbers to the command (again, these are my keys from my error. Make sure to use your own):


    The output should look like this:


    Then you should have no more errors!
    Thanks, helped me fix after I deleted my jaunty keys.
    To err is human, but not uniquely so.

  3. #3
    Join Date
    Dec 2007
    Location
    Parkland...
    Beans
    199
    Distro
    Ubuntu

    Re: HOWTO: Fix GPG errors for bad/deleted keys

    I'm doing this with Karmic.

    I imported the key, but am stuck with 'BADSIG 40976EAF437D05B5'

    This wasn't fixed by re-importing the key!

  4. #4
    Join Date
    Mar 2006
    Location
    Canada
    Beans
    1,313
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: HOWTO: Fix GPG errors for bad/deleted keys

    Quote Originally Posted by ben2talk View Post
    I'm doing this with Karmic.

    I imported the key, but am stuck with 'BADSIG 40976EAF437D05B5'

    This wasn't fixed by re-importing the key!
    Here's a little tutorial that you might find useful: http://www.drewwithers.com/content/h...g-error-badsig

  5. #5
    Join Date
    Dec 2009
    Beans
    1

    Re: HOWTO: Fix GPG errors for bad/deleted keys

    I have heard that this key loss thing is happening a lot when upgrading to 9.10, Being new to Ubuntu, I was really glad to find this fix because it works perfectly. Thank You! I'm really getting impressed with this Linux stuff.....

  6. #6
    Join Date
    Feb 2009
    Beans
    4

    Re: HOWTO: Fix GPG errors for bad/deleted keys

    This is the new address for the blog site to fix the error

    http://www.drewwithers.com/2009/12/h...or-badsig.html

  7. #7
    Join Date
    Jan 2010
    Beans
    1

    Re: HOWTO: Fix GPG errors for bad/deleted keys

    Worked great! Thanks

  8. #8
    Join Date
    Mar 2010
    Location
    Copenhagen, Denmark
    Beans
    2
    Distro
    Ubuntu 9.10 Karmic Koala

    Re: HOWTO: Fix GPG errors for bad/deleted keys

    First, thank you for the good thread. Secondly, the command could be used also if you don't have any imported key. I succeed to import wine key to my repositories.
    Thanks again man !

  9. #9
    Join Date
    Apr 2009
    Beans
    5

    Red face Re: HOWTO: Fix GPG errors for bad/deleted keys

    Quote Originally Posted by altonbr View Post
    I don't know what I did, but one day I started using Ubuntu and all my public signature keys for downloading software were all deleted.

    This error popped up after running "System > Administration > Update Manager"


    The fix for this is to re-download the keys using the hexidecimal numbers given in the error (I bolded them above).

    NOTE: Your hexadecimal numbers may be different then mine, so make sure to use the hexadecimals numbers in your error, not mine.

    Type this command into the terminal ("Applications > Accessories > Terminal")
    Code:
    sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys
    And then add the hexadecimal numbers to the command (again, these are my keys from my error. Make sure to use your own):


    The output should look like this:


    Then you should have no more errors!
    I have a similar problem. When I ran the command as you described, here is what I got:

    sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 40976EAF437D05B5
    Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --keyserver keyserver.ubuntu.com --recv-keys 40976EAF437D05B5
    gpg: requesting key 437D05B5 from hkp server keyserver.ubuntu.com
    gpg: [don't know]: invalid packet (ctb=2f)
    gpg: keydb_get_keyblock failed: eof
    gpg: [don't know]: invalid packet (ctb=2f)
    gpg: /etc/apt/trusted.gpg: copy to `/etc/apt/trusted.gpg.tmp' failed: invalid packet
    gpg: error writing keyring `/etc/apt/trusted.gpg': invalid packet
    gpg: [don't know]: invalid packet (ctb=2f)
    gpg: keydb_search failed: invalid packet
    gpg: key 437D05B5: public key "[User ID not found]" imported
    gpg: error reading `[stream]': invalid packet
    gpg: Total number processed: 0
    gpg: imported: 1

    Any idea what's going on here and how to fix it?

    Thanks

    mm

  10. #10
    Join Date
    Apr 2010
    Beans
    57

    Thumbs up Re: HOWTO: Fix GPG errors for bad/deleted keys

    Thanks a bunch! I was getting these errors on Karmic, after updating Mythbuntu through auto-builds.

    After running the command to re-import the keys, I can now actually believe it when it says there are no updates available!

Page 1 of 5 123 ... LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •