NO_PUBKEY E88979FB9B30ACF2

[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]

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 

===========================
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( manpage for repository creation and user configuration details.