Chrome NO_PUBKEY E88979FB9B30ACF2

[Dan Brown]

I have the same problem. I thought I had a perfect install for me but after timeshifting back through 10 days I realised that from the beginning I was getting these errors. I don't even want Chrome anyway as everything is in Firefox. Clean install and LL won't do the first update of 443 Updates.

I have fast reliable Fibre and good local repos and and just when I thought my distro hopping days were over LL changes to Chrome.

Here's a log before I do anything except run TimeShift and Clonezilla to Back up this Virgin install

============ Log ===========

Hit:1 http://security.ubuntu.com/ubuntu jammy-security InRelease
Get:2 https://dl.google.com/linux/chrome/deb stable InRelease [1,825 B]
Hit:3 http://archive.canonical.com/ubuntu jammy InRelease
Hit:4 http://repo.linuxliteos.com/linuxlite fluorite InRelease
Err:2 https://dl.google.com/linux/chrome/deb stable InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E88979FB9B30ACF2
Hit:5 http://us.archive.ubuntu.com/ubuntu jammy InRelease
Hit:6 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:7 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy InRelease
Hit:8 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease
Reading package lists...
W: GPG error: https://dl.google.com/linux/chrome/deb stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E88979FB9B30ACF2
E: The repository 'https://dl.google.com/linux/chrome/deb stable InRelease' is not signed.

DB