Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#78097 - [systemd] 253.2-1: Executing "systemctl daemon-reexec" causes GNOME session to crash

Attached to Project: Arch Linux
Opened by Pascal Ernster (hardfalcon) - Sunday, 02 April 2023, 07:08 GMT
Last edited by Christian Hesse (eworm) - Monday, 03 April 2023, 14:54 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Christian Hesse (eworm)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

With systemd 253.2-1 installed and running, when I execute "systemctl daemon-reexec", my GNOME session crashes either immediately or as soon as I press Ctrl+C inside a terminal, even after that "systemctl daemon-reexec" command has finished/returned successfully and there is no process inside the shell to be killed/cancelled by pressing Ctrl+C.

When I downgrade all systemd packages to 253.1-3 (and lib32-systemd to 253.1-1), my GNOME session crashes again at first because systemd 253.2-1 is still running and due to "systemctl daemon-reexec" being executed as part of the package's post-install hook, but after that, I can re-login into GNOME and execute "systemctl daemon-reexec" without causing that GNOME session to crash.
This task depends upon

Closed by  Christian Hesse (eworm)
Monday, 03 April 2023, 14:54 GMT
Reason for closing:  Fixed
Additional comments about closing:  systemd 253.2-2
Comment by Pascal Ernster (hardfalcon) - Sunday, 02 April 2023, 10:25 GMT
I've bisected this down to https://github.com/systemd/systemd/commit/0417b2875521424104d27229c13681c03baf9290, and I've opened a bug report about this in upstream's issue tracker:
https://github.com/systemd/systemd/issues/27106
Comment by Pascal Ernster (hardfalcon) - Sunday, 02 April 2023, 11:06 GMT
Recompiled systemd 253.2-1 packages with commits e32df1d6d86b221a983ba0c76f507b38cfb78fb6, 0e3706f770b7efaa6b70dc4e5b0c30bef34dccae and 0417b2875521424104d27229c13681c03baf9290 reverted (the first two are required to be able to cleanly revert the last one) fix the issue for me.
Comment by Pascal Ernster (hardfalcon) - Sunday, 02 April 2023, 11:39 GMT
Recompiled systemd 253.2-1 packages with https://github.com/systemd/systemd/pull/27107 applied on top also solves the issue for me.

//EDIT: Upstream have merged the pull request, so the fix can now be applied by simply adding the line "4f44d2c4f76922a4f48dd4473e6abaca40d7e555" to the _backports array inside the PKGBUILD when rebuilding the systemd packages.
Comment by Christian Hesse (eworm) - Monday, 03 April 2023, 07:17 GMT
This is already in `v253-stable` now. We will see a new tag really soon, I will probably wait for that.
Comment by Christian Hesse (eworm) - Monday, 03 April 2023, 14:53 GMT
Still no tag, so cherry-picking.

Loading...