22

Every time I attempt to perform a software update I get this error from the software manager:

W:GPG error: http://download.virtualbox.org/virtualbox/debian xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A2F683C52980AECF, W:The repository 'http://download.virtualbox.org/virtualbox/debian xenial InRelease' is not signed., W:Data from such a repository can't be authenticated and is therefore potentially dangerous to use., W:See apt-secure(8) manpage for repository creation and user configuration details., W:There is no public key available for the following key IDs:
A2F683C52980AECF  , W:The repository 'http://ppa.launchpad.net/blackmage/f.lux/ubuntu xenial Release' does not have a Release file., W:Data from such a repository can't be authenticated and is therefore potentially dangerous to use., W:See apt-secure(8) manpage for repository creation and user configuration details., W:The repository 'http://ppa.launchpad.net/gezakovacs/ppa/ubuntu xenial Release' does not have a Release file., W:Data from such a repository can't be authenticated and is therefore potentially dangerous to use., W:See apt-secure(8) manpage for repository creation and user configuration details., W:The repository 'http://ppa.launchpad.net/zeal-developers/ppa/ubuntu xenial Release' does not have a Release file., W:Data from such a repository can't be authenticated and is therefore potentially dangerous to use., W:See apt-secure(8) manpage for repository creation and user configuration details., W:http://deb.playonlinux.com/dists/trusty/InRelease: Signature by key 74F7358425EEB6176094C884E0F72778C4676186 uses weak digest algorithm (SHA1), W:http://liveusb.info/multisystem/depot/dists/all/Release.gpg: Signature by key 32027DE3D67157C45E69C0AE4E940D7FDD7FB8CC uses weak digest algorithm (SHA1), W:http://vagrant-deb.linestarve.com/dists/any/InRelease: Signature by key AD319E0F7CFFA38B4D9F6E55CE3F3DE92099F7A4 uses weak digest algorithm (SHA1), E:Failed to fetch http://ppa.launchpad.net/blackmage/f.lux/ubuntu/dists/xenial/main/source/Sources  404  Not Found, E:Failed to fetch http://ppa.launchpad.net/blackmage/f.lux/ubuntu/dists/xenial/main/binary-i386/Packages  404  Not Found, E:Failed to fetch http://ppa.launchpad.net/gezakovacs/ppa/ubuntu/dists/xenial/main/binary-i386/Packages  404  Not Found, E:Failed to fetch http://ppa.launchpad.net/zeal-developers/ppa/ubuntu/dists/xenial/main/source/Sources  404  Not Found, E:Failed to fetch http://ppa.launchpad.net/zeal-developers/ppa/ubuntu/dists/xenial/main/binary-i386/Packages  404  Not Found, E:Some index files failed to download. They have been ignored, or old ones used instead.

Here are some screenshots of what is displayed when I attempt to edit the repositories I have:

enter image description here

enter image description here

enter image description here

enter image description here

enter image description here

enter image description here

enter image description here

I am not certain how to fix this.

4 Answers 4

16

In the command-line type this content:

wget -q http://download.virtualbox.org/virtualbox/debian/oracle_vbox_2016.asc -O- | sudo apt-key add -
0
10

You need to remove the old keys left over from before the upgrade. Do:

sudo apt-key list

Find the offending key (near "virtualbox", after "pub", xxx/KEYHERE) and do:

sudo apt-key del KEYHERE

Then go to https://www.virtualbox.org/wiki/Linux_Downloads and follow the instructions at "Debian-based Linux distributions"

2
  • Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference.
    – MadMike
    Jun 9, 2016 at 17:04
  • Whilst I can't argue with that logic, the info you're suggesting to include is open to change, so I don't see that it's particularly helpful to do so in the long term.
    – NikLP
    Jun 13, 2016 at 9:56
3

You obviously did a system upgrade without having removed the external repositories before. The easiest way to solve the problem would be to remove all external repositories and delete all related public keys. After having done this, update the repositories (sudo apt-get update) and check whether everything is fixed now ... and when no error occurs anymore, you can add new external repositories, but carefully check whether these repositories are "matching Xenial" ...

Depending on which repositories you add, a "weak signature" warning still may appear when updating the repositories - but you can ignore it, because it is just an informational message.

gpg: Signature by key ... uses weak digest algorithm (SHA1)  
2
  • Does this remove the repositories that some software needs to update? Feb 20, 2017 at 9:29
  • @TylerDurden Sorry, I don't understand what you mean ... "this" does nothing ... it is an explanation and a suggestion. When you remove external repositories you remove only them and the standard repositories still exist. After a system upgrade you can re-add the external repositories - in case they contain software for the upgraded system. :)
    – cl-netbox
    Feb 20, 2017 at 12:52
1

I encounter this problem when trying to install docker. The instruction advices to run lsb_release -cs and it returns me serena, but it should xenial so I manually open file /etc/apt/sources.list.d/additional-repositories.list and have changed: serena -> xenial in the next string:

deb [arch=amd64] https://download.docker.com/linux/ubuntu serena stable

the problem has gone

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .