Devuan bug report logs - #900
procps: w does not query elogind for sessions

Package: procps; Maintainer for procps is Devuan Dev <devuan-dev@lists.dyne.org>; Source for procps is src:procps.

Reported by: Andrew Bower <andrew@bower.uk>

Date: Sun, 27 Jul 2025 22:50:01 UTC

Severity: grave

Found in version 2:4.0.4-8devuan1

Fixed in version 2.41-5devuan2

Done: dak@devuan.org

Full log

🔗 View this message in rfc822 format

X-Loop: owner@bugs.devuan.org
Subject: bug#900: procps: w does not query elogind for sessions
Reply-To: Andrew Bower <andrew@bower.uk>, 900@bugs.devuan.org
Resent-From: Andrew Bower <andrew@bower.uk>
Resent-To: devuan-bugs@lists.dyne.org
Resent-CC: Devuan Dev <devuan-dev@lists.dyne.org>
X-Loop: owner@bugs.devuan.org
Resent-Date: Sat, 09 Aug 2025 21:24:01 +0000
Resent-Message-ID: <handler.900.B900.175477456412216@bugs.devuan.org>
Resent-Sender: owner@bugs.devuan.org
X-Devuan-PR-Message: followup 900
X-Devuan-PR-Package: procps
X-Devuan-PR-Keywords: 
References: <aIfYMj-jSJbNoPZx@arden.ab8.net> <aIieJYSAP9eVSiyg@hindley.org.uk> <aIkujJEowteSzgya@shenstone.ab8.net> <aIuZjUI-ttE5Qa_o@hindley.org.uk> <aIvwXGoQ2izucZfR@shenstone.ab8.net> <175365644638.7806.4267640139913169199.reportbug@arden.ab8.net> <aJZyko8XZuADzuut@arden.ab8.net> <aJZ05pD7Z3sLMNCV@arden.ab8.net> <aJds06g7j58C78s-@hindley.org.uk> <aJellJyM7j5kZroP@arden.ab8.net> <175365644638.7806.4267640139913169199.reportbug@arden.ab8.net>
X-Devuan-PR-Source: procps
Received: via spool by 900-submit@bugs.devuan.org id=B900.175477456412216
          (code B ref 900); Sat, 09 Aug 2025 21:24:01 +0000
Received: (at 900) by bugs.devuan.org; 9 Aug 2025 21:22:44 +0000
Delivered-To: bugs@devuan.org
Received: from email.devuan.org [2a01:4f9:fff1:13::5fd9:f9e4]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Sat, 09 Aug 2025 21:22:44 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id GTd5GR28l2jwIAAAmSBk0A
	(envelope-from <andrew@bower.uk>)
	for <bugs@devuan.org>; Sat, 09 Aug 2025 21:22:37 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 4EB964A2; Sat,  9 Aug 2025 21:22:37 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS,
	T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2a00:1098:0:82:1000:0:2:1; helo=mx2.mythic-beasts.com; envelope-from=andrew@bower.uk; receiver=<UNKNOWN> 
Received: from mx2.mythic-beasts.com (mx2.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1])
	by email.devuan.org (Postfix) with ESMTPS id 062893B
	for <900@bugs.devuan.org>; Sat,  9 Aug 2025 21:22:35 +0000 (UTC)
Received: by mailhub-hex-d.mythic-beasts.com with esmtpsa  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <andrew@bower.uk>)
	id 1ukr1P-00CdBI-0m;
	Sat, 09 Aug 2025 22:22:35 +0100
Received: from ajb85 by arden.ab8.net with local (Exim 4.98.2)
	(envelope-from <andrew@bower.uk>)
	id 1ukr1M-000000004nb-1kcA;
	Sat, 09 Aug 2025 22:22:32 +0100
Date: Sat, 9 Aug 2025 22:22:32 +0100
From: Andrew Bower <andrew@bower.uk>
To: Mark Hindley <mark@hindley.org.uk>
Cc: 900@bugs.devuan.org
Message-ID: <aJe8GCR2OMTwfBEP@arden.ab8.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <aJellJyM7j5kZroP@arden.ab8.net>
User-Agent: Mutt/2.2.13 (2024-03-09)
X-BlackCat-Spam-Score: 0

On Sat, Aug 09, 2025 at 08:46:28PM +0100, Andrew Bower wrote:
> On Sat, Aug 09, 2025 at 04:44:19PM +0100, Mark Hindley wrote:
> > On Fri, Aug 08, 2025 at 11:06:30PM +0100, Andrew Bower wrote:
> > > https://git.devuan.org/devuan/util-linux/pulls/1
> > 
> > Thanks
> > 
> > Isn't
> > 
> > -	log_utmp(&cxt);
> > +	log_utmp(&cxt);
> > 
> > no-op?
> 
> Yes! My patch is a crude edit of Chris's patch to neutralise this
> removal but it is valid and works.
> 
> I think in retrospect that it might be clearer to have another quilt
> patch layered on top of his patch.

I've reworked https://git.devuan.org/devuan/util-linux/pulls/1 to create
a patch that explicitly restores the utmp writing rather than editing a
debian patch. I think this is clearer now what has happened, if you read
the series:

debian/login-turn-off-btmp-utmp-lastlog-writing.patch
..
devuan/restore-utmp-writing.patch

> > Do we need to restore the lastlog and btmp entries as well?
> > 
> > Perhaps we just drop the whole patch?
> 
> Lastlog was already written by pam_lastlog.so before trixie and the
> replacement is pam_lastlog2. The tooling to read btmp was removed by
> util-linux.
> 
> So I'm not sure there would be any benefit from reversing the rest of
> the patch to be worth the increased delta from Debian. Bear in mind that
> the patch wasn't just about dropping utmp, it was also about taking over
> login from another source package.
> 
> An alternative approach I considered was to include code to read the
> systemd-style login records directly in 'w' but that seemed like too
> much for a patch and it would certainly take more time!

Send a report that this bug log contains spam.

Devuan bug report logs - #900 procps: w does not query elogind for sessions

Devuan bug report logs - #900
procps: w does not query elogind for sessions