Re: systemd --user managers after systemd upgrade

[Luca Boccassi <luca.boccassi@xxxxxxxxx>]

On Sat, 29 Jun 2024 at 21:16, Mike Gilbert <floppym@xxxxxxxxxx> wrote:
>
> I recently added systemd v256 to Gentoo's ebuild repo. While testing
> the upgrade process from v255, I have run into an issue.
>
> After the upgrade, my KDE Plasma session stopped working, and I was
> unable to execute a reboot from the GUI.
>
> Looking at the journal, I see several messages like this one:
>
> Jun 29 14:21:30 naomi systemd[2387904]:
> /usr/lib/systemd/systemd-executor (deleted): error while loading
> shared libraries: libsystemd-core-255.so: cannot open shared object
> file: No such file or directory
>
> It appears to be executing a deleted binary
> (/usr/lib/systemd/systemd-executor), likely via /proc/1/fd/..., and
> then fails when loading a deleted shared library
> (libsystemd-core-255.so).
>
> The new versions of these files do exist on the filesystem. Also, I
> was able to reboot the system by switching to a text console and
> pressing ctrl-alt-delete.
>
> Any idea what happened here? I'm not sure if this is a systemd bug, or
> if I missed something in my packaging script (ebuild).

This is a known issue, your packaging scripts _must_ reexec both the
system instance and all user instances. For the latter you can just
do:

systemctl kill --kill-whom='main' --signal='SIGRTMIN+25' 'user@*.service'