Google Chrome for Linux Saying "No Public Key"

[Gerowen]

So I had a strange issue today while installing Google Chrome on a Debian machine.  I kept getting an error when manually checking for updates in the terminal with "apt-get update" telling me there was no public key for something.  I started disabling 3rd party repositories and found out the problem was coming from Google Chrome's repository.  Normally the deb file from google(dot)com/chrome automagically sets up the repository, adds the public signing key, etc. so that the end user doesn't have to do anything other than install regular system updates when they're available and Chrome will get pulled in with everything else.  In this case however, for whatever reason, the deb I downloaded today (28 April 2016, Chrome version 50.0.2661.86 (64-bit)) didn't add the signing key.  It added the repository, but without the key my system kept warning me there was no public key available for the repository.

 

If you run into this issue, Google has a page set up specifically for showing you how to manually add the public signing key for your particular package manager.  You can find it here: http://www.google.com/linuxrepositories/

 

I just wanted to share this little tidbit of info in case anybody else runs into this problem.  When the error first popped up in the terminal it didn't tell me "which" repository was having a problem, just that one of them was missing the public key, so I narrowed it down by manually disabling the repositories (removing the 3rd party files from /etc/apt/sources.list.d) until the error went away.

[Mindovermaster Moderator]

Very interesting.... Never heard this before.... Thanks for the link, though.

[Obi-Wan Kenobi]

23 hours ago, Gerowen said:

So I had a strange issue today while installing Google Chrome on a Debian machine.  I kept getting an error when manually checking for updates in the terminal with "apt-get update" telling me there was no public key for something.  I started disabling 3rd party repositories and found out the problem was coming from Google Chrome's repository.  Normally the deb file from google(dot)com/chrome automagically sets up the repository, adds the public signing key, etc. so that the end user doesn't have to do anything other than install regular system updates when they're available and Chrome will get pulled in with everything else.  In this case however, for whatever reason, the deb I downloaded today (28 April 2016, Chrome version 50.0.2661.86 (64-bit)) didn't add the signing key.  It added the repository, but without the key my system kept warning me there was no public key available for the repository.

 

If you run into this issue, Google has a page set up specifically for showing you how to manually add the public signing key for your particular package manager.  You can find it here: http://www.google.com/linuxrepositories/

 

I just wanted to share this little tidbit of info in case anybody else runs into this problem.  When the error first popped up in the terminal it didn't tell me "which" repository was having a problem, just that one of them was missing the public key, so I narrowed it down by manually disabling the repositories (removing the 3rd party files from /etc/apt/sources.list.d) until the error went away.

Man, good job. And also, I love your setup, too! (Watched your youtube vid) That's awesome!

[Boo Berry]

Related issue, if you're using Ubuntu 16.04, Linux Mint 17.x, Debian Stretch, etc. You'll start encountering a warning saying gpgv:/var/lib/apt/lists/partial/dl.google.com_linux_chrome_deb_dists_stable_Release.gpg: The repository is insufficiently signed by key 4CCA1EAF950CEE4AB83976DCA040830F7FAC5991 (weak digest). This is due to the depreciation of SHA-1 and currently Google Chrome's repository is half broken because of this (as are other repos).

 

https://wiki.debian.org/Teams/Apt/Sha1Removal

 

https://bugs.chromium.org/p/chromium/issues/detail?id=596074

 

Using one of these workarounds will fix it once Google fixes everything on their side (as I said, still half broken). It *should* also fix the OP's issue;

sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 1397BC53640DB551

Or...

wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | sudo apt-key add -

 

Edited April 30, 2016 by Boo Berry