Bugzilla – Bug 1217771
Please add support for systemd-logind in utempter
Last modified: 2023-12-27 10:06:50 UTC
Curently the utempter helper isn't work anymore due to the migration from utmp/wtmp support to systemd-logind. It would be nice to have a support for systemd-logind in (lib)utempter as well as currently no login session via e.g. XTerm is seen anymore.
(In reply to Dr. Werner Fink from comment #0) > Curently the utempter helper isn't work anymore due to the migration from > utmp/wtmp support to systemd-logind. It would be nice to have a support > for systemd-logind in (lib)utempter as well as currently no login session via > e.g. XTerm is seen anymore. With systemd-logind we don't need libutempter anymore, libsystemd is taking over. As explained in my talks and mails, xterm is not visible anymore because it is no login session, systemd-logind explicit rejects all additions which are not a new login session (don't remember currently anymore how it checks it, somehow if the PID is a new group or so). Historically xterm only created a utmp entry so that the user could see the wall messages. This needs to be solved by the Desktop environment (e.g. on GNOME you will not see any wall messages, the sender get's only an error, on KDE you get flooded with this wall messages...).
I'm using the option -ls for XTerm aka use a login shell to be able to see wall messages ... now the feature is simply dropped?
One other problem is that the implementation of read_utmp_from_systemd() for coreutils (GPL-3.0-or-later) can be ported to tcsh this is BSD-3-Clause