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

Message #13 received at 900@bugs.devuan.org (full text, mbox, reply):

Received: (at 900) by bugs.devuan.org; 28 Jul 2025 20:07:34 +0000
Return-Path: <andrew@bower.uk>
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); Mon, 28 Jul 2025 20:07:34 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id 48+ZDjjYh2h6VgAAmSBk0A
	(envelope-from <andrew@bower.uk>)
	for <bugs@devuan.org>; Mon, 28 Jul 2025 20:06:16 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 211FE585; Mon, 28 Jul 2025 20:06:16 +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 DD15337
	for <900@bugs.devuan.org>; Mon, 28 Jul 2025 20:06:14 +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 1ugU6w-00EIkM-07;
	Mon, 28 Jul 2025 21:06:14 +0100
Received: from ajb85 by arden.ab8.net with local (Exim 4.98.2)
	(envelope-from <andrew@bower.uk>)
	id 1ugU6s-000000001ct-3dU6;
	Mon, 28 Jul 2025 21:06:10 +0100
Date: Mon, 28 Jul 2025 21:06:10 +0100
From: Andrew Bower <andrew@bower.uk>
To: Mark Hindley <mark@hindley.org.uk>
Cc: 900@bugs.devuan.org
Subject: Re: bug#900: procps: w does not query elogind for sessions
Message-ID: <aIfYMj-jSJbNoPZx@arden.ab8.net>
References: <175365644638.7806.4267640139913169199.reportbug@arden.ab8.net>
 <aIdUCiy-f5zBOGGe@hindley.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <aIdUCiy-f5zBOGGe@hindley.org.uk>
User-Agent: Mutt/2.2.13 (2024-03-09)
X-BlackCat-Spam-Score: 0

Hi Mark,

On Mon, Jul 28, 2025 at 11:42:19AM +0100, Mark Hindley wrote:
> Thanks for this. You have been folowwing this area more closely than me. 

Unfortunately I haven't been on top of the utmp or lastlog side of this
transition even though I did adopt wtmpdb with a view to mitigating user
experiences with that change.

> I believe the original impetus to remove libsystemd linkage from procps 
> was to reduce libsystemd infiltration into 'core' utilities. 

I am all in favour of that ambition. I don't think the key
building-block packages should depend on libsystemd, hence my
disappointment when coreutils recently gained the dependency (should we
be forking that?)

> Devuan systems without elogind are viable (I use sway/seatd as my daily 
> driver) so just adding elogind support to procps isn't a universal 
> solution.

Does sway/seatd write to utmp? Does it do anything else?

> Do you have a suggestion or idea as to a way forward?

I see we have forked util-linux, so one thing we could do is to fix the
build of login(1) to restore writing to utmp, for virtual console
logins. That assumes that this is what has actually been broken - I
haven't checked yet.

I think that still leaves session manager entries missing (I seem to get
one for Debian/lightdm but not Devuan/slim). openssh seems to behave
well with regard to utmp.

If we are going to make continued use of utmp we should really try to
sort out any packages that don't realise struct utmp now has unsigned
seconds (converts the y1901/y2038 problem into a y1969/y2160 problem),
but that's not immediately practical. (IMO that would have been a better
use of Debian development time than excising "legacy" usage, which could
have waited another release cycle while the replacements proved and
improved themselves...)

Now, is there anything we can do with elogind-captured sessions without
linking with libsystemd0? Well, maybe... I'm thinking about options! But
to be honest, probably not in time for Excalibur.

Andrew

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