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

Launchpad Bug Tracker 2054761 at bugs.launchpad.net
Tue Jun 4 19:47:26 UTC 2024


This bug was fixed in the package systemd - 255.4-1ubuntu8.1

---------------
systemd (255.4-1ubuntu8.1) noble; urgency=medium

  * debian/systemd-resolved.postinst: ignore cp failure (LP: #2047975)
  * debian/systemd.postinst: don't restart user managers if too old (LP: #2054761)
  * switch-root: use MS_MOVE for /run when switchig from initrd (LP: #2064096)
  * test: check for kernel.apparmor_restrict_unprivileged_userns (LP: #2065964)

 -- Nick Rosbrook <enr0n at ubuntu.com>  Fri, 17 May 2024 10:47:34 +0200

** Changed in: systemd (Ubuntu Noble)
       Status: Fix Committed => Fix Released

-- 
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 Released

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




More information about the foundations-bugs mailing list