GPG errors key: What they are and how to fix them

Ubuntu and update errors are inseparable. Every now and then I encounter errors while updating the system after adding a new source. The other day I was trying to install Mate desktop environment when I got this GPG error while updating the system:

How to Fix GPG errors key

Download Zip

The public signing key that Google issues to sign and authenticate packages distributed through its Linux repositories has changed, resulting in users, perhaps yourself included, seeing various errors thrown up by the package manager.

Now you can run apt update with no warnings or errors related to deprecated key configurations. We apt users just need to remember to adjust any old installation instructions that depend on apt-key. Instead of using apt-key, you must instead install a key to /etc/apt/trusted.gpg.d/ or /etc/apt/keyrings/, using gpg as needed.

GPG (GNU Privacy Guard) errors when running apt-get update in a Docker container may occur if the GPG keys used to verify the packages are not available on the system. This can happen if the keys have expired or if the package repository has been modified.

It is always a good idea to run apt-get update before installing packages in a Docker container to ensure that you have the latest package information from the repository. This can help prevent errors and ensure that you have the latest versions of the packages you are installing.

This is because Nvidia is changing their public keys for their repositories, see the details here.The instructions in the original post does not work for me. I still see errors after running the command.Since I am building a Docker image, I followed the instructions here and it works:

On 2021-11-21 4:35 p.m., Cubic PPA wrote:> Your question #699574 on Cubic changed:> +question/699574>> Status: Open => Answered>> Cubic PPA proposed the following answer:> All the missing packages you listed are in the universe repository.>> [4]> The dependency errors may be fixed using:>> $ sudo apt-add-repository universe>> Otherwise, you can manually add the universe repository by using nano to> edit:>> /etc/apt/sources.list> ...or...> /etc/apt/sources.list.d/official-package-repositories.list>> (Note: I think Linux Mint uses official-package-> repositories.list).>> [5]> I think Linux Mint 19.x is based on Ubuntu 18.04 "Bionic Beaver".>> Your sources should look something like this:>> deb bionic universe> deb bionic-updates universe> deb bionic-backports main restricted universe multiverse> deb bionic-security universe>> [6]> Update your packages cache:>> $ sudo apt update>> [7]> Optionally, I suggest upgrading all your packages to the latest available versions.>> $ sudo apt upgrade>> [8]> After you've resolved all of your package dependencies, there is one more issue you will run into on Linux Mint.>> Cubic needs the base-files package version based systems) or the qemu-system-gui package version >=1:4.2.>> In Linux Mint 19.x, this base-files package is labeled as version> "19.3.1" (!!!), and this confuses the Cubic installer.>> To work around this, we can temporarily install a "fake" qemu-system-gui> package to circumvent the package dependency.>> $ sudo apt-get install equivs> $ cd /Documents> $ equivs-control qemu-system-gui> $ sed -i "s^Package.*Package: qemu-system-guig" qemu-system-gui> $ sed -i "s^# Version.*Version: 1:4.2g" qemu-system-gui> $ equivs-build qemu-system-gui> $ sudo dpkg -i qemu-system-gui_4.2_all.deb>> [9]> Install Cubic>> $ sudo apt install --no-install-recommends cubic>> [10]> Finally, uninstall the "fake" qemu-system-gui package, while keeping Cubic.>> $ sudo dpkg -r --force depends qemu-system-gui>

sudo rm -r /etc/pacman.d/gnupgsudo pacman-key --initsudo pacman-key --populate manjarosudo pacman-key --populate archlinuxsudo pacman -Syvv manjaro-keyring # for testing, if everything is okay there will be no errors

Based on your output there are no errors on update so we expect the update to have succeeded. Verify with dpkg. I believe "apt-get update" is silent so you would not see any non-Warning or above messages.

Other files than these may be referenced in the error message. They can be fixed by editing the file which is producing errors manually. Open the file as root and look for these entries (there should be 3):

Thank you, that worked around the issue, permitting YUM to function again. Then tried the full fix of retrieving and reinstalling AnyDesk's GPG key: no errors popped up with the wget and the rpm --import but the error returned at next YUM operation, so that will have to remain disabled. We'll try refreshing everything at next product update and maybe the key will be ok by then. 2ff7e9595c