Hello Valentin, On Wed, Nov 12, 2025 at 01:05:29PM +0100, Valentin Haudiquet wrote: > [...] > > Do you see any suspicious lines in the output of the "w", "who", > > and/or "last" commands? I.e., any entry in the TTY column that does > > not look like a TTY, or a missing entry in that column? > > Yes ! w and who are normal, but last shows: > ``` > [vhaudiquet@x1c inetutils <merge-lp2130124-resolute>]$ last > vhaudiqu tty2 tty2 Thu Nov 6 12:00 - still logged in > vhaudiqu seat0 login screen Thu Nov 6 12:00 - still logged in > [...] > ```
I am still trying to understand where these entries come from. The Gnulib code used by GNU Inetutils for reading utmp information without the /var/run/utmp file, but with "configure --enable-systemd", can synthesize "seatN" and probably "sshd" entries for the .ut_line field. This should be the cause for the observed test failures. On Ubuntu 22.04, the "last" program comes from the "util-linux" package, the "w" program comes the "procps" package, and the "who" program from the "coreutils" package. On Ubuntu 26.04, "last" might come from the "wtmpdb" package, and "who" might come from the "rust-coreutils". Of these, only "coreutils" is an obvious candidate for using the same Gnulib code as GNU Inetutils. Are the results for "who" from "rust-coreutils" and "coreutils" identical for the in development Ubuntu 26.04 distribution? > However, that is also the case on Questing and older Ubuntu releases. > And to my understanding that is normal :) I'd say this happened after removing /var/run/utmp, as at least Ubuntu 22.04, still having /var/run/utmp, does not show these utmp entries. > [...] > Something must have changed, that before did not pick up those > sessions and now picks them up instead of the right one ? It seems to me as if replacing /var/run/utmp with the "wtmpdb" mechanism might have been this change. This seems to have introduced the utmp entries that misdirect syslogd, resulting in errors while using them and thus triggering test failures. Thanks, Erik
