I ran this command in the Terminal:
sudo apt-get update
Updating ends with the following error report:
W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://extras.ubuntu.com precise Release: The following signatures were invalid: BADSIG 16126D3A3E5C1192 Ubuntu Extras Archive Automatic Signing Key <[email protected]>
W: GPG error: http://ppa.launchpad.net precise Release: The following signatures were invalid: BADSIG 4C1CBC1B69B0E2F4 Launchpad PPA for Jonathan French
W: Failed to fetch http://extras.ubuntu.com/ubuntu/dists/precise/Release
What does this mean and why is it happening?
Try this:
This message is displaying because the gpg key for that repository is missing in your apt-key database.
To import the key, open a terminal and enter these commands
pgp keys are mostly distributed in several keystore. Ubuntu related keys are usually found in
keyserver.ubuntu.com
. But if that fails you can use alternatives. Like -You must replace the alphanumeric part, with the specific key. Make sure the key is one you trust. Any repository with this key, would be able to install any package without warning.
You would see the following output if the above is successful
Then run this command:
Note the
-
sign afteradd
.Then
sudo apt-get update
, you will have no such messages after this.I ran into this issue an older Ubuntu 16.04 box. My keys weren't expired so I wasn't really sure why I was getting the error. I tried SirCharlo's method but I still got the same errors. Being this particular error is coming from the 'Ubuntu Extras Archive Automatic Signing Key' I decided to refresh my keys. After doing that everything worked fine. Not sure if it was a combination of both method's but if SirCharlo's method doesn't work, run this command:
I found that just running these commands worked for me.
You can try my script to automatically receive all GPG keys for PPAs you use: smartupdate.sh.
It will launch
apt-get update
, then find all GPG errors and receive keys for found GPG signatures. In your case, it will just launchbut when you add a few unsigned PPAs, it becomes boring to add GPG keys manually. :)
I got a similar error. But instead of
BADSIG
I gotKEYEXPIRED
for the PostgreSQL repo:The solution is perfectly described here but this is what I did to solve it:
And now
$ sudo apt-get update
will work perfectly!The following commands solved the problem for me:
This tip (from actionparsnip) worked for me:
Found in:
https://answers.launchpad.net/ubuntu/+source/update-manager/+question/194077
This could be due to a caching issue of a HTTP proxy. If you have one of those somewhere along the route like me, you can run
apt
and circumvent the cache temporarily:DON'T DO THIS (the accepted answer here):
Because it creates a new problem, in the process of fixing your problem.
You need to preserve the existing ownership and permissions of the
lists
folder.So instead, as 131 suggests in a comment above, do it this way:
tl;dr