Upgrade from 18.04?

[GregM]

Uninstalled Google Earth and now it says

greg@greg-OptiPlex-990:~$ sudo apt-get update && sudo apt-get dist-upgrade
Hit:1 http://us.archive.ubuntu.com/ubuntu bionic InRelease
Get:2 https://brave-browser-apt-release.s3.brave.com stable InRelease [4,317 B]
Hit:3 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:4 http://security.ubuntu.com/ubuntu bionic-security InRelease
Hit:5 http://ppa.launchpad.net/bablu-boy/nutty.0.1/ubuntu bionic InRelease
Hit:6 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease
Err:2 https://brave-browser-apt-release.s3.brave.com stable InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A8580BDC82D3DC6C
Fetched 4,317 B in 1s (4,885 B/s)
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://brave-browser-apt-release.s3.brave.com stable InRelease: The fol
lowing signatures couldn't be verified because the public key is not available: NO_PUBKEY A8580BDC82D3DC6C
W: Failed to fetch https://brave-browser-apt-release.s3...able/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A8580BDC82D3DC6C
W: Some index files failed to download. They have been ignored, or old ones used instead.
E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
greg@greg-OptiPlex-990:~$

What am I doing wrong?

[claydoh]

Tried to update with the suggested command got this

greg@greg-OptiPlex-990:~$ sudo apt-get update && sudo apt-get dist-upgrade

Get:1 http://dl.google.com/linux/earth/deb stable InRelease [1,807 B]

Hit:2 http://us.archive.ubuntu.com/ubuntu bionic InRelease
Get:3 https://brave-browser-apt-release.s3.brave.com stable InRelease [4,317 B]
Err:1 http://dl.google.com/linux/earth/deb stable InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 78BD65473CB3BD13

Hit:4 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:5 http://security.ubuntu.com/ubuntu bionic-security InRelease
Hit:6 http://ppa.launchpad.net/bablu-boy/nutty.0.1/ubuntu bionic InRelease

Hit:7 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease
Err:3 https://brave-browser-apt-release.s3.brave.com stable InRelease

The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A8580BDC82D3DC6C

Reading package lists... Done

W: GPG error: http://dl.google.com/linux/earth/deb stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 78BD65473CB3BD13

E: The repository 'http://dl.google.com/linux/earth/deb stable InRelease' is no longer 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.

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://brave-browser-apt-release.s3.brave.com stable InRelease: The fol
lowing signatures couldn't be verified because the public key is not available: NO_PUBKEY A8580BDC82D3DC6C

greg@greg-OptiPlex-990:~$ ^C

Ok, the warnings are saying that Google Earth's and Brave Broser's signing keys are outdated. Seems to happen to both of these somewhat often.
As the messages say, they are simply being ignored when updating.

These are easily Google-able, especially as Google Earth's error happened over a year ago ( they let the key expire, iirc):

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

For Brave Browser:

curl -s https://brave-browser-apt-release.s3.brave.com/brave-core.asc | sudo apt-key --keyring /etc/apt/trusted.gpg.d/brave-browser-release.gpg add -

And update again. This should fi=x the errors, which probably would not have effected the upgrade as these external repos would be disabled during the upgrade process.
You may want to reinstall both GE and Brave from fresh packages to make sure these are set up for updates properly after the upgrade, particularly if you are not seeing updates to the browser at all.

You will also need to re-add any PPAs you have added in the past (if you added any), if the owners of those are still up and running and providing packages for 20.04.

[GregM]

What a stressful day.
I think I have done it but had to fiddle with it as it conked out at 99%.

I'm glad this only happens every few years.
Thanks for the help

[chimak111]

So you're still on 18.04?

Running

sudo apt-get update && sudo apt-get dist-upgrade

would not move you up to 20.04 aka Focal Fossa.

See https://help.ubuntu.com/community/AptGet/Howto

Running

lsb_release -a

would be useful.

[claydoh]

So you're still on 18.04?

Running

sudo apt-get update && sudo apt-get dist-upgrade

would not move you up to 20.04 aka Focal Fossa.

See https://help.ubuntu.com/community/AptGet/Howto

Running

lsb_release -a

would be useful.

He is following the official upgrade directions I linked to, which do explicitly tell you to update fully before running the upgrade tool

[chimak111]

He is following the official upgrade directions I linked to, which do explicitly tell you to update fully before running the upgrade tool

Oops! My bad!

[GregM]

Mission accomplished and it seems to be working correctly so far.
Thanks for the help.

[claydoh]