Hi, On Wed, Nov 12, 2025 at 01:05:29PM +0100, Valentin Haudiquet wrote: > > > Since the testing user is only notified when VERBOSE=yes, this should not > > happen with just "make TESTS=syslogd.sh check", i.e., that should pass. > > Indeed, it's a PASS on my machine.
Thanks for the confirmation! > > 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 > vhaudiqu tty2 tty2 Sat Nov 1 19:03 - still logged in > vhaudiqu seat0 login screen Sat Nov 1 19:03 - still logged in > vhaudiqu tty2 tty2 Tue Oct 28 11:39 - still logged in > vhaudiqu seat0 login screen Tue Oct 28 11:39 - still logged in > vhaudiqu tty2 tty2 Tue Oct 28 07:02 - still logged in > vhaudiqu seat0 login screen Tue Oct 28 07:02 - still logged in > vhaudiqu tty2 tty2 Mon Oct 27 17:36 - still logged in > vhaudiqu seat0 login screen Mon Oct 27 17:36 - still logged in > vhaudiqu tty2 tty2 Mon Oct 27 16:44 - still logged in > vhaudiqu seat0 login screen Mon Oct 27 16:44 - still logged in > vhaudiqu tty2 tty2 Tue Oct 7 17:11 - still logged in > vhaudiqu seat0 login screen Tue Oct 7 17:11 - still logged in > vhaudiqu tty2 tty2 Thu Oct 2 23:13 - still logged in > vhaudiqu seat0 login screen Thu Oct 2 23:13 - still logged in > vhaudiqu tty2 tty2 Thu Oct 2 14:29 - still logged in > vhaudiqu seat0 login screen Thu Oct 2 14:29 - still logged in > vhaudiqu tty2 tty2 Thu Oct 2 14:26 - still logged in > vhaudiqu seat0 login screen Thu Oct 2 14:26 - still logged in > vhaudiqu tty2 tty2 Thu Oct 2 12:34 - still logged in > vhaudiqu seat0 login screen Thu Oct 2 12:34 - still logged in > vhaudiqu tty2 tty2 Thu Oct 2 12:00 - still logged in > vhaudiqu seat0 login screen Thu Oct 2 12:00 - still logged in > vhaudiqu tty2 tty2 Thu Oct 2 11:50 - 11:59 (00:09) > vhaudiqu seat0 login screen Thu Oct 2 11:50 - still logged in > vhaudiqu tty2 tty2 Thu Oct 2 11:35 - still logged in > vhaudiqu seat0 login screen Thu Oct 2 11:35 - still logged in > vhaudiqu tty2 tty2 Thu Oct 2 11:20 - still logged in > vhaudiqu seat0 login screen Thu Oct 2 11:20 - still logged in > ``` That could be the source for "seat0" and the resulting "/dev/seat0" on that system. It does seem possible that the autopktest system has entries with "sshd" that result in "/dev/sshd". > However, that is also the case on Questing and older Ubuntu releases. > And to my understanding that is normal :) I would assume that my Ubuntu 18.04 system back in 2022 also showed non TTY entries in "last", but I did not keep relevant logs from back then. I only see "ttyN" and "pts/N" (with N a number) in the output on my Ubuntu 22.04 system and on several headless Debian systems I have SSH access to. > On the autopkgtest, the VERBOSE variable is set, and my guess is that > the machine running those being a server and not a desktop, there is > no "seat0" but "sshd" sessions arround, which explains that error. That seems plausible to me, too. > Something must have changed, that before did not pick up those > sessions and now picks them up instead of the right one ? Or possibly in addition to the right one? As I understand the syslogd code, it attempts to send a copy of the message to each currently logged in session of the user. > I'm not sure indeed which part of the system handles that, but I will > try to reproduce on different versions of Ubuntu with different > versions of the package and keep you posted. Thanks, Erik
