Status update utmp to logind migration

Hi, I wanted to give a short update about the status of our migration from utmp to logind: This week we released systemd v254, which allows to use logind as source for user sessions instead of /run/utmp. With the last snapshot, an additional chunk of packages prefering logind over utmp got released. Since not all tools are adjusted, /run/utmp will stay at first as fallback for this tools, which are not yet converted. Even if the list of known packages is rather small. But mid-term, we will not create /run/utmp anymore. For more details, there is still my blog: https://www.thkukuk.de/blog/Y2038_glibc_utmp_64bit/ And the recording of my talk at All Systems Go! this week: https://media.ccc.de/v/all-systems-go-2023-183-y2038-replace-utmp-with-login... Regards, Thorsten PS: the who/uptime seg.fault with gdm as login manager some people are currently seeing is not a direct result of this, since who/uptime are still using /run/utmp. This seems to be a result of the readutmp rewrite in gnulib to be able to support logind. Question is, why this only happens with gdm and not KDE, login, sshd, ... -- Thorsten Kukuk, Distinguished Engineer, Senior Architect, Future Technologies SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nuernberg, Germany Managing Director: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg)
participants (1)
-
Thorsten Kukuk