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

[Łukasz Zemczak]

Hello Daniel, or anyone else affected,

Accepted systemd into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/255.4-1ubuntu8.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed verification-needed-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