I believe I figured out what is happening here. In systemd v250, systemd
user managers began interpreting the signal RTMIN+25 as a command to
daemon-reexec. This was done so that:
systemctl kill --kill-whom='main' --signal='SIGRTMIN+25'
'user@*.service'
could be used as a way to reexec all user instances at once. So,
systemd.postinst now contains such a line so that user managers are also
reexec'd during package upgrades.
However, since Jammy is running systemd v249, the running user manager
at the time of the upgrade does not have this reexec logic, and appears
to behave as if it were killed normally. So, the fix should be to not
attempt to restart all the user managers if the old version is too old.
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Tags added: systemd-sru-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054761
Title:
gnome-shell crashed with signal 5: Settings schema
'org.gnome.mutter.wayland' does not contain a key named 'xwayland-
allow-byte-swapped-clients'
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2054761/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
