On 2025-02-17 00:33:59 +0100, Chris Hofstaedtler wrote:
> * Vincent Lefevre <vinc...@vinc17.net> [250217 00:28]:
> > On 2025-02-16 23:56:43 +0100, Chris Hofstaedtler wrote:
> > > * Michael Stone <mst...@debian.org> [250216 22:45]:
> > > > On Sun, Feb 16, 2025 at 07:05:13PM +0100, Vincent Lefevre wrote:
> > > > > No, w(1) is broken (at least in sid). See the difference between
> > > > > "who" and "w" with systemd 256.7-1, i.e. before the upgrade of
> > > > > systemd that removed utmp support:
> > > > 
> > > > That's because someone decided to suddenly remove an interface which has
> > > > been used for decades without any kind of transition plan or 
> > > > replacement.
> > > 
> > > Clearly there is a replacement, because the data is there:
> > > 
> > >   % w
> > >   23:53:23 up 1 min,  2 users,  load average: 0.06, 0.03, 0.00
> > >   USER     TTY      FROM             LOGIN@   IDLE   JCPU PCPU WHAT
> > >   ch                192.168.64.1     23:53    1:24 0.00s  0.02s 
> > > sshd-session: ch [priv]
> > >   ch                -                23:53    1:24 0.00s  0.04s 
> > > /usr/lib/systemd/systemd --user
> > 
> > No data for xterm. Other terminals are affected too, such as
> > GNOME Terminal.
> 
> AFAIK this is expected. You should have a single entry for the X
> session, if you started it from a session manager.

This means that it is no longer possible to get information that
could be obtained previously: IDLE, JCPU, PCPU, WHAT associated
with the terminal. Unless there is another tool to get such
useful information, this is a regression.

And what about non-X terminals, such as provided by GNU Screen?
(That said, GNU Screen does not work in a consistent way in
Debian/stable.)

> Did you file a bug with mosh for investigation?

Just done: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096161

-- 
Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)

Reply via email to