Ubuntu
ubuntu-release-upgrader package

ubuntu upgrade from 20.04 to 22.04 is failing

Bug #2039891 reported by Manu Singhal on 2023-10-19

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	ubuntu-release-upgrader (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

ubuntu upgrade from 20.04 to 22.04 is failing.
following are the error log from apt.log

dist-upgrade tail -f /var/log/dist-upgrade/apt.log
  MarkKeep xserver-xorg-input-libinput:amd64 < 0.29.0-1 -> 1.2.1-1 @ii umU Ib > FU=0
Investigating (9) gnome-calendar:amd64 < 3.36.2-0ubuntu1 -> 41.2-3 @ii umU Ib >
Broken gnome-calendar:amd64 Depends on libgweather-3-16:amd64 < 3.36.1-1~ubuntu20.04.1 | 40.0-5build1 @ii umH > (>= 40.0)
  Considering libgweather-3-16:amd64 20 as a solution to gnome-calendar:amd64 1
  MarkKeep gnome-calendar:amd64 < 3.36.2-0ubuntu1 -> 41.2-3 @ii umU Ib > FU=0
  Holding Back gnome-calendar:amd64 rather than change libgweather-3-16:amd64
Try to Re-Instate (9) mutter:amd64
  MarkKeep mutter:amd64 < 3.36.9-0ubuntu0.20.04.2 -> 42.9-0ubuntu5 @ii umU Ib > FU=0
Done
Log time: 2023-10-20 03:19:45.886317

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.41
ProcVersionSignature: Ubuntu 5.15.0-87.97~20.04.1-generic 5.15.122
Uname: Linux 5.15.0-87-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 03:20:10 2023
InstallationDate: Installed on 2021-09-15 (764 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to focal on 2023-10-19 (0 days ago)
mtime.conffile..etc.update-manager.release-upgrades: 2023-10-20T01:59:38.508862

Tags:

Revision history for this message

Manu Singhal (manusinghal19) wrote on 2023-10-19:

CurrentDmesg.txt.txt Edit (95.0 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.4 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (325 bytes, text/plain; charset="utf-8")
VarLogDistupgradeAptclonesystemstate.tar.gz Edit (645.2 KiB, application/x-gzip)
VarLogDistupgradeAptlog.txt Edit (252.0 KiB, text/plain; charset="utf-8")
VarLogDistupgradeLspcitxt.txt Edit (2.7 KiB, text/plain; charset="utf-8")
VarLogDistupgradeMainlog.txt Edit (15.0 KiB, text/plain; charset="utf-8")
modified.conffile..etc.update-manager.release-upgrades.txt Edit (822 bytes, text/plain; charset="utf-8")

Revision history for this message

Erich Eickmeyer (eeickmeyer) wrote on 2023-10-20:

There's a lot to unpack here. First, the apt.log tail is a red herring. There were a LOT of failures further before that in your apt.log. The /var/log/dist-upgrade/main.log was a lot more telling:

2023-10-20 03:19:43,098 WARNING Can't mark 'ubuntu-desktop' for upgrade (E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.)
2023-10-20 03:19:43,398 ERROR Dist-upgrade failed: 'Broken packages after upgrade: evolution-data-server, gnome-control-center, libgirepository-1.0-1, ubuntu-desktop'

Even further up, I noticed a lot of PPAs that got deactivated. PPAs sometimes have interfering packages which can cause this very situation. A good tool in the Ubuntu repositories is `ppa-purge` which can disable and remove packages that were installed by the addition of a PPA, and is highly recommended prior to trying a Release Upgrade. The command syntax is as easy as `sudo ppa-purge ppa:{ppa username/ppa name}`.

The removal of those and all third-party repositories are highly recommended before attempting a release upgrade to prevent problems like this from happening as ubuntu-release-upgrader cannot account for third party repositories or packages.

Furthermore, it appears as though your /etc/update-manager/release-upgrades has been set to `Prompt=normal` when this would be expected to be `Prompt=lts` when moving from LTS to LTS. While this might not be a factor, it is slightly suspicious and not the default for this type of upgrade.

Unfortunately, this doesn't appear to be a bug in ubuntu-release-upgrader, but a package conflict with existing packages on the system.

Changed in ubuntu-release-upgrader (Ubuntu):
status:	New → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntuubuntu-release-upgrader package