How to fix: GPG keys for Google Chrome are already installed but they are not correct.

By Edgars AbolinsLast updated on:

In some specific cases when trying to install Google Chrome on a RHEL based Linux system via terminal, you might face an error similar to this:

GPG key at https://dl.google.com/linux/linux_signing_key.pub (0xD38B4796) is already installed
The GPG keys listed for the “google-chrome” repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.

This indicates that your system has outdated Google GPG (GNU Privacy Guard) keys installed and you should remove them first before attempting to install the Google Chrome browser.

  1. First use this command to check what kind of GPG keys you have installed on your system:
rpm -q gpg-pubkey --qf '%{NAME}-%{VERSION}-%{RELEASE}\t%{SUMMARY}\n'

2. Check in the returned results if you have these two specific GPG keys:

gpg-pubkey-7fac5991-4615767f gpg (Google, Inc. Linux Package Signing Key )
gpg-pubkey-d38b4796-570c8cd3 gpg (Google Inc. (Linux Packages Signing Authorit y) linux-packages-keymaster@google.com)

3. Remove them by using these commands:

sudo rpm --erase --allmatches gpg-pubkey-7fac5991-4615767f
sudo rpm --erase --allmatches gpg-pubkey-d38b4796-570c8cd3

4. Try installing Google Chrome again:

sudo dnf install google-chrome-stable

 

2 Comments on How to fix: GPG keys for Google Chrome are already installed but they are not correct.
About the author
Edgars Abolins Edgars Abolins, author at DoinWP.com
I'm a full-stack WordPress developer with a 10+ years of solid experience in the core web development languages, development processes / techniques, web security, Linux server management and with pretty good understanding about proper semantics, UX/UI, technical SEO, good design and basic knowledge of company leadership. On top of that - a distant 5+ years experience as a computer and electronics repair technician which often enables me to understand also how the things work at the hardware level.

2 thoughts on “How to fix: GPG keys for Google Chrome are already installed but they are not correct.”

  1. I had this error multiple times over the last two years in my RHEL9 installation – when updating/upgrading with the dnf package manager. Your guide to solving it is goog. I might only add the error is likely repeat with package updates, however the solution is as you present. To me, it seems Google and/or RH stopped wanting to pay attention to what each other is doing, and RH expects their corporate customer IT departments to pay for support 😉

    Reply

    1. Hey Fred, Thank you for your feedback, happy to hear that the solution is useful! 🙂 If you or anyone else has some ideas on how to improve this guide to completely solve this repetitive problem, feel free to share and I’ll be honored to add your reference in this article.

      Also if you guys have some other struggles regarding this, please mention them and I’ll try to find a solution.

      Reply
Your feedback matters!…
I hope you found this article helpful. Feel free to add some comments - your feedback is very important to me, as it drives my motivation and helps me to improve the content.