Ubuntu
ubuntu-release-upgrader package

System installed from jammy point release iso cannot upgrade to noble

Bug #2054319 reported by Tim Andersson
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Invalid
Undecided
Unassigned
policykit-1 (Ubuntu)
Invalid
Undecided
Unassigned
ubuntu-release-upgrader (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

We have different crashes being encountered. In our auto-upgrade-testing, we see gnome-shell crash, however, when testing locally, I didn't experience this. @hyask did experience the gnome-shell crash though.

When running an upgrade from jammy to noble in a virsh vm, about halfway through the upgrade process my gui dies. I then ran the upgrade from a console, to which it revealed that just the gui dies - the upgrade process, for me, continues and then laterally fails.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubuntu-release-upgrader-core 1:24.04.7
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu7
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
CrashReports:
 640:1000:124:1592041:2024-02-19 14:26:22.564354912 +0000:2024-02-19 14:51:56.318947066 +0000:/var/crash/_usr_libexec_tracker-extract-3.1000.crash
 600:0:124:833806:2024-02-19 14:34:18.370597600 +0000:2024-02-19 14:34:19.370597600 +0000:/var/crash/polkitd.0.crash
Date: Mon Feb 19 14:53:39 2024
InstallationDate: Installed on 2024-02-19 (0 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to noble on 2024-02-19 (0 days ago)
VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: pkexec must be setuid root
VarLogDistupgradeXorgFixuplog:
 INFO:root:/usr/bin/do-release-upgrade running
 INFO:root:No xorg.conf, exiting
mtime.conffile..etc.init.d.apport: 2024-02-14T15:51:44

Revision history for this message
Tim Andersson (andersson123) wrote :
Revision history for this message
Steve Langasek (vorlon) wrote :

Which ISO, specifically? The already released point release ISO, or the candidate image for the next one?

(And if it's the candidate, is this reproducible with the last point release iso?)

summary: - jammy point release iso cannot upgrade to noble
+ System installed from jammy point release iso cannot upgrade to noble
Revision history for this message
Tim Andersson (andersson123) wrote :

One of two crash files

Revision history for this message
Tim Andersson (andersson123) wrote :

the other crash file

Revision history for this message
Tim Andersson (andersson123) wrote :

Candidate image for the point release, I'll test the image from the last point release now

Revision history for this message
Tim Andersson (andersson123) wrote :

I've also tested upgrading from mantic to noble as well and that seems perfectly fine

Revision history for this message
Tim Andersson (andersson123) wrote :

 Failed to check if group polkitd already exists: Connection refused

 id: ‘polkitd’: no such user
 chown: invalid group: ‘root:polkitd’
 dpkg: error processing package polkitd (--configure):
  installed polkitd package post-installation script subprocess returned error exit status 1

Revision history for this message
Skia (hyask) wrote :

Maybe not related to latest point iso in particular, since the problem seems a bit more generic on my side: upgrading desktop image from Jammy to Noble breaks with `gnome-shell` crash (linked in attachment), along with the tracker-extract-3 crash already mentionned.
This reproduces both locally with a manual `sudo do-release-upgrade -d` in a Gnome Terminal, and in Jenkins running auto-upgrade-testing tool, but both images came from preinstalled cloud images, upgraded to latest Jammy, so none installed from point release iso.

Revision history for this message
Skia (hyask) wrote :

Here are the Jenkins artifacts of the run with the `gnome-shell` crash.

Revision history for this message
Tim Andersson (andersson123) wrote :

I tested with the iso from the previous point release and ran into the same issues.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please use 'ubuntu-bug' to report each crash file so the robots can analyse and classify them.

Skia (hyask)
tags: added: rls-nn-incoming
Revision history for this message
Skia (hyask) wrote :

Yeah, sorry, I forgot to mention. The crashes that happen in our Jenkins are already pushed to the error tracker.
Here are links to the latest oopses:
gnome-shell: https://errors.ubuntu.com/oops/af2e99fc-d101-11ee-8a58-fa163ec8ca8c
tracker-extract: https://errors.ubuntu.com/oops/7c05a805-d101-11ee-8a58-fa163ec8ca8c

Maybe Tim will have a link for the polkit crash, but I couldn't find one.

Julian Andres Klode (juliank)
no longer affects: tracker-miners (Ubuntu)
Revision history for this message
Brian Murray (brian-murray) wrote :

I broke out the policykit failure, with an apport-package bug, into https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2054716

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The tracker-extract crash may be bug 1990630 or bug 1962585, because it looks like both fixes haven't made it into jammy yet. But also this bug list probably needs some maintenance: https://bugs.launchpad.net/ubuntu/+source/tracker-miners

The gnome-shell crash is now tracked in bug 2054761.

Revision history for this message
Julian Andres Klode (juliank) wrote :

Deferring tracking to the other bugs

Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Invalid
Changed in policykit-1 (Ubuntu):
status: New → Invalid
Changed in gnome-shell (Ubuntu):
status: New → Invalid
tags: removed: rls-nn-incoming
Revision history for this message
Martin Malec (martin-malec) wrote :

Having the same issue as in #7 (id: ‘polkitd’: no such user, chown: invalid group: ‘root:polkitd’). Managed to apply workaround to move with the test upgrade from this stuck place by creating polkitd system group using `groupadd -r polkitd`.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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