unable to upgrade for no specified reason
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-release-upgrader (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Run in terminal and got
Checking package manager
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating the changes
Calculating the changes
Could not determine the upgrade
An unresolvable problem occurred while calculating the upgrade.
If none of this applies, then please report this bug using the
command 'ubuntu-bug ubuntu-
you want to investigate this yourself the log files in
'/var/log/
Specifically, look at 'main.log' and 'apt.log'.
main.log gives
ERROR Dist-upgrade failed: 'Broken packages after upgrade: ubuntu-desktop'
I'd tried it before and was having ppa-purge notifications which I've solved
I see various broken messages in apt.log (not clear which is causing the problem! or whether it's an observation and the upgrade is solving via the update)the last is:
Broken ubuntu-
Considering gnome-shell-
Try to Re-Instate (3) gir1.2-
MarkKeep gir1.2-
Done
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: ubuntu-
ProcVersionSign
Uname: Linux 6.2.0-39-generic x86_64
ApportVersion: 2.26.1-0ubuntu2.1
Architecture: amd64
CasperMD5CheckR
CrashDB: ubuntu
CrashReports:
600:113:
640:1000:
664:1000:
640:1000:
CurrentDesktop: KDE
Date: Thu Dec 14 17:50:04 2023
InstallationDate: Installed on 2017-07-22 (2336 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitec
SourcePackage: ubuntu-
UpgradeStatus: Upgraded to lunar on 2023-12-14 (0 days ago)
VarLogDistupgra
Start-Date: 2023-12-14 16:50:03
Requested-By: robert (1000)
End-Date: 2023-12-14 16:50:04
VarLogDistupgra
Log started: 2023-12-14 16:50:03
Log ended: 2023-12-14 16:50:04
I tried again a few times in one case removing gir1.2-gdm (see above) first which removed quite a few other things. Still got a failure. But today it works and I'm now on 23.10. I guess a fix has also solved this! Many thanks. This can be closed (wasn't certain what final status to give it...)!