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

[Nick Rosbrook]

This is not a problem for oracular, because no supported upgrade paths
to oracular would have an old enough systemd to hit this.

** Also affects: mutter (Ubuntu Noble)
   Importance: Undecided
       Status: New

** Also affects: gnome-shell (Ubuntu Noble)
   Importance: Undecided
       Status: New

** Also affects: systemd (Ubuntu Noble)
   Importance: Undecided
       Status: New

** Changed in: systemd (Ubuntu Noble)
       Status: New => In Progress

** Changed in: systemd (Ubuntu Noble)
   Importance: Undecided => High

** Changed in: systemd (Ubuntu Noble)
     Assignee: (unassigned) => Nick Rosbrook (enr0n)

** Changed in: systemd (Ubuntu)
       Status: Triaged => Invalid

-- 
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 gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in gnome-shell source package in Noble:
  New
Status in mutter source package in Noble:
  New
Status in systemd source package in Noble:
  In Progress

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/gnome-shell/+bug/2054761/+subscriptions