Chrome NO_PUBKEY E88979FB9B30ACF2

[DesertWinds]

New linux user beginning to regret changing from windows, but staying open.

Cant update software seems a public keys issue.

Changed to better closer server, same error

speed checked net, is fine

tried codes in other fixes on this forum, same errors

log below ..help  :o

===========================
Install Updates Error log
===========================
Install Updates could not fetch the package cache information lists.
Go to https://www.linuxliteos.com/forums/ and paste the log below into a new or existing thread for assistance.

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

Hit:1 http://ubuntu.mirror.serversaustralia.com.au/ubuntu jammy InRelease
Hit:2 http://ubuntu.mirror.serversaustralia.com.au/ubuntu jammy-updates InRelease
Hit:3 http://ubuntu.mirror.serversaustralia.com.au/ubuntu jammy-backports InRelease
Hit:4 http://ubuntu.mirror.serversaustralia.com.au/ubuntu jammy-security InRelease
Get:5 https://dl.google.com/linux/chrome/deb stable InRelease [1,825 B]
Hit:6 http://repo.linuxliteos.com/linuxlite fluorite InRelease
Err:5 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:7 http://archive.canonical.com/ubuntu jammy 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.

from Terminal same error

sudo apt update
[sudo] password for geoff:
Hit:1 http://ubuntu.mirror.serversaustralia.com.au/ubuntu jammy InRelease
Hit:2 http://ubuntu.mirror.serversaustralia.com.au/ubuntu jammy-updates InRelease
Hit:3 http://ubuntu.mirror.serversaustralia.com.au/ubuntu jammy-backports InRelease
Hit:4 http://ubuntu.mirror.serversaustralia.com.au/ubuntu jammy-security InRelease
Hit:5 http://repo.linuxliteos.com/linuxlite fluorite InRelease               
Get:6 https://dl.google.com/linux/chrome/deb stable InRelease [1,825 B]       
Err:6 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:7 http://archive.canonical.com/ubuntu jammy InRelease
Reading package lists... Done
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.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

[stevef]

There may be a problem with the source repository - it is giving a 404 error which is odd..
I expect they will resolve it in due course.

In the short term - if you need to allow the updates to run, try this.

Click Menu and begin typing 'Software & Updates' in the search box
When you see 'Software & Updates' click on it.
In the Window that opens select 'Other Software' tab

Uncheck the entry for Chrome and enter your password to authenticate the change if asked.
Click Close on the 'Software & Updates' window and then 'Reload' to refresh the cache.

Then try update/upgrade again.  This should now skip the Chrome update.

Once done, I'd leave it 24 hours or so, then go through the above again but re-enable the Chrome repository.

If it isn't working then let us know.

[DesertWinds]

Thanks Stevef it works :045:

There may be a problem with the source repository - it is giving a 404 error which is odd..
I expect they will resolve it in due course.

In the short term - if you need to allow the updates to run, try this.

Click Menu and begin typing 'Software & Updates' in the search box
When you see 'Software & Updates' click on it.
In the Window that opens select 'Other Software' tab

Uncheck the entry for Chrome and enter your password to authenticate the change if asked.
Click Close on the 'Software & Updates' window and then 'Reload' to refresh the cache.

Then try update/upgrade again.  This should now skip the Chrome update.

Once done, I'd leave it 24 hours or so, then go through the above again but re-enable the Chrome repository.

If it isn't working then let us know.

[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

[stevef]

It's working ok for my system so possibly a problem at the server end on the repository you are being directed to.
Have you really had this problem for 10 or more days, or just got it now ?

If you follow the instructions in reply 1, you should be able to update/upgrade by skipping the Chrome for the short term.

To check you have the correct key, please can you open a terminal - by pressing Ctrl Alt and T together.
In the terminal window type or paste in this command followed by Enter.

Code:

apt-key list

This will show what keys apt can find to check software is signed - the chrome section is the one we need to see..
Copy the output and paste it back here.

Chrome has been the included browser for Linux Lite since the release of LL6.0 in June 2022 when Firefox went snap so it has not just happened.
For those that still want Firefox, it is offered in Lite Software, but this will install Snap.
As an alternative, check the 6.0 release notes which give a method to install without Snap.