Pages

Tuesday, August 30, 2011

Fixing GPG Keys in UBUNTU


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

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 .
Type this command into the terminal ("Applications > Accessories > Terminal" OR press "Ctrl-Alt-Del")
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 6D975C4791E7EE5E 5A9BF3BB4E5E17B5 7FB8BEE0A1F196A8"


The output should look like this:

"gpg: requesting key 437D05B5 from hkp server keyserver.ubuntu.com"


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











http://ubuntuforums.org/showthread.php?t=1221323

14 comments:

  1. Thank you! Very helpful!

    ReplyDelete
  2. I've same problem, i googling for the troubleshooting, Finally i found your blog's that help for me, thank's a lot.

    ReplyDelete
  3. شكرا لك حبي
    thank you very much friend

    ReplyDelete
  4. THANK YOU SO MUCH! i fixed the error with your blog.. more power to you

    ReplyDelete
  5. hm, i tried that but got the message: key 0BB65... not found on keyserver

    do you have an idea where the problem is?

    ReplyDelete
  6. Salvou minha vida :D

    ReplyDelete
  7. tried this but got the message: key ---------- not found on keyserver

    do you have an idea where the problem is?

    ReplyDelete
  8. This fixed my issue. Thanks for the tip!

    ReplyDelete