cannot upgrade to 24.04 says their are unsupported launchpads

[Richard Seitz]

This was caused by:
* Upgrading to a pre-release version of Ubuntu
This is most likely a transient problem,
please try again later.
If none of this applies, then please report this bug using the
command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If
you want to investigate this yourself the log files in
'/var/log/dist-upgrade' will contain details about the upgrade.
Specifically, look at 'main.log' and 'apt.log'.

Restoring original system state

Aborting
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: ubuntu-release-upgrader-core 1:23.10.14
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Uname: Linux 6.5.0-28-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Wed May 1 16:24:33 2024
InstallationDate: Installed on 2022-12-15 (503 days ago)
InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to mantic on 2024-05-01 (0 days ago)
VarLogDistupgradeAptHistorylog:
 Start-Date: 2024-05-01 16:23:45
 Requested-By: rick (1000)
 End-Date: 2024-05-01 16:23:45
VarLogDistupgradeApttermlog:
 Log started: 2024-05-01 16:23:45
 Log ended: 2024-05-01 16:23:45

[Richard Seitz (rwseitz3060)]

I added the dist-upgrade main.log for review.

[Richard Seitz (rwseitz3060)]

i cleaned my cache and now I get
Error during update

A problem occurred during the update. This is usually some sort of
network problem, please check your network connection and retry.

Restoring original system state

Aborting
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done

network connection is fine and working correctly

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.