[Bug 2054761] Re: Dist upgrades from Jammy to Noble crash [Oh no! Something has gone wrong.]

[Nick Rosbrook]

I have verified the fix using systemd 255.4-1ubuntu8.1 from noble-
proposed. On a Jammy Desktop system, I simply ran an upgrade:


nr at clean-jammy-amd64:~$ wget http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz
--2024-05-22 11:45:16--  http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz
Resolving archive.ubuntu.com (archive.ubuntu.com)... 91.189.91.82, 185.125.190.36, 91.189.91.83, ...
Connecting to archive.ubuntu.com (archive.ubuntu.com)|91.189.91.82|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1274850 (1.2M) [application/x-gzip]
Saving to: \u2018noble.tar.gz\u2019

noble.tar.gz        100%[===================>]   1.21M  --.-KB/s    in
0.1s

2024-05-22 11:45:16 (9.20 MB/s) - \u2018noble.tar.gz\u2019 saved
[1274850/1274850]

nr at clean-jammy-amd64:~$ tar xf noble.tar.gz 
nr at clean-jammy-amd64:~$ sudo -E ./noble --frontend DistUpgradeViewNonInteractive
[ ... ]

The upgrade proceeded without issue. Namely, my session was not killed
during the upgrade.

nr at clean-jammy-amd64:~$ apt policy systemd
systemd:
  Installed: 255.4-1ubuntu8.1
  Candidate: 255.4-1ubuntu8.1
  Version table:
 *** 255.4-1ubuntu8.1 500
        500 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     255.4-1ubuntu8 500
        500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages


** Tags removed: verification-needed-noble
** Tags added: verification-done-noble

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2054761

Title:
  Dist upgrades from Jammy to Noble crash [Oh no! Something has gone
  wrong.]

Status in mutter package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in mutter source package in Noble:
  Invalid
Status in systemd source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  During upgrades from Jammy to Noble, systemd.postinst trys to reexec all running user managers. It does so using a feature that was not added until v250, and attempting this against a v249 daemon results in it being killed instead, which brings down all user sessions.

  Hence, during the upgrades, the user session is killed, and the system
  is left in a bad state.

  [Test Plan]

  Run an upgrade from Jammy to Noble on Ubuntu desktop. The upgrade
  should proceed normally (or at least not have the entire session
  killed by systemd.postinst).

  [Where problems could occur]

  The fix is to add a version guard against this logic in
  systemd.postinst. If the version string was wrong or typo'd, the fix
  would not work as expected.

  [Original Description]

  Feb 21 21:39:12 autopkgtest gnome-shell[17945]: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients'
  Feb 21 21:39:12 autopkgtest gnome-session-binary[17908]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5
  Feb 21 21:39:12 autopkgtest gnome-shell[17959]: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients'
  Feb 21 21:39:12 autopkgtest gnome-session-binary[17908]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5

  https://errors.ubuntu.com/problem/bf714caff944bed915a3c4321664107c65547d1f
  https://errors.ubuntu.com/problem/db8f7e3dfc79e658b9b2aa8c596b014ce4b9f217
  https://errors.ubuntu.com/oops/af2e99fc-d101-11ee-8a58-fa163ec8ca8c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054761/+subscriptions