REpository upgrade?

[ohjrson]

There seems to be a mixture of symptoms about an in-series upgrade and a definite problem with Team Viewer.

What version of Linux Lite do you think you were running before attempting the in-series upgrade? A-6.4
If you have you already tried a manual in-series upgrade, please explain how and what happened. A-When I clicked on the settings, Lite upgrade = a window that says No need to upgrade you are already running the latest release.

If there is any confusion about what version of Linux Lite you are running there are some quick checks you can do.
Open a terminal (press three keys 'Ctrl' 'Alt' 'T' together) and in the window that opens type these commands followed by return.

Code:

inxi -S

Code:

cat /etc/llver

A- All confirm v6.4 LL

In my upgrade it does not say upgrade to 6.6 just 6.4

This suggests you may be looking at the 'Lite Welcome' screen of a 6.2 system.  Can you confirm where you see this please ?

When I try the seris upgrade it says I am running the current version.

What do you do to see this message ? (eg from Upgrading using the Lite Welcome screen or by clicking 'Menu'-> 'Settings'-> 'Lite Upgrade' or some other way.) A-By clicking Settings>Lite Upgrade

It also looks like you have a problem doing a routine update, upgrade cycle due to the Team Viewer problem.
How long have you had this issue ? A-As far as I know just this attempt to do an upgrade.
I have tried to install updates and I get an error saying there are problems.
This is what I get:

===========================
Install Updates Error log
===========================
Install Updates could not fetch the package cache information lists.
Go to https://www.freecinema2022.gq/forums/ and paste the log below into the Software - Support - Updates section for assistance.

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

Hit:1 http://mirror.clarkson.edu/linux-lite fluorite InRelease
Hit:2 http://archive.canonical.com jammy InRelease
Hit:3 http://archive.ubuntu.com/ubuntu jammy InRelease
Hit:4 http://archive.ubuntu.com/ubuntu jammy-security InRelease
Hit:5 https://repo.skype.com/deb stable InRelease
Hit:6 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:7 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
Hit:8 https://linux.teamviewer.com/deb stable InRelease
Get:9 https://linux.teamviewer.com/deb preview InRelease [10.2 kB]
Err:10 https://linux.teamviewer.com/deb development InRelease
  403  Forbidden [IP: 2600:9000:26c2:b400:1c:3aaa:b100:93a1 443]
Err:9 https://linux.teamviewer.com/deb preview InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C5E224500C1289C0
Hit:11 https://dl.google.com/linux/chrome/deb stable InRelease
Hit:12 http://repository.spotify.com stable InRelease
Reading package lists...
W: https://repo.skype.com/deb/dists/stable/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
E: Failed to fetch https://linux.teamviewer.com/deb/dists/d.../InRelease  403  Forbidden [IP: 2600:9000:26c2:b400:1c:3aaa:b100:93a1 443]
E: The repository 'https://linux.teamviewer.com/deb development InRelease' is not signed.
W: GPG error: https://linux.teamviewer.com/deb preview InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C5E224500C1289C0
E: The repository 'https://linux.teamviewer.com/deb preview InRelease' is not signed.


The Team Viewer forum has several reports of this problem - I've not looked at them all, but for example this thread suggests there was a temporary problem earlier this year

Code:

https://community.teamviewer.com/English/discussion/128826/cannot-update-on-ubuntu-repository-is-no-longer-signed

Whereas this thread suggests a couple of methods adding the key.

Code:

https://community.teamviewer.com/English/discussion/126616/official-repo-public-key-not-available

You may want to review  their forum to find a trusted solution. But I'd suggest this needs to be sorted before trying to do any in-series upgrade.

Clearly Team viewer has an issue so I will try to uncheck that repository and try again.
Thanks for your help