Devuan bug report logs - #302
elogind: doesn't seem to be updating lastlog

Package: elogind; Reported by: "Dimitris T." <>;
Date: Thu, 7 Mar 2019 16:18:01 UTC;
Done: Mark Hindley <>;
Maintainer for elogind is (unknown).

View this report as an mbox folder.

Notification sent to "Dimitris T." <>:
bug acknowledged by developer. Full text available.

Message sent:

From: (Devuan bug Tracking System)
To: "Dimitris T." <>
Subject: bug#302 acknowledged by developer

This is an automatic notification regarding your bug report
#302: elogind: doesn't seem to be updating lastlog,
which was filed against the elogind package.

It has been closed by one of the developers, namely
Mark Hindley <>.

Their explanation is attached below.  If this explanation is
unsatisfactory and you have not received a better one in a separate
message then please contact the developer, by replying to this email.

Devuan Bugs Owner
(administrator, Devuan bugs database)

Received: (at 302-done) by; 17 Apr 2019 10:30:05 +0000
Return-Path: <>
Received: from []
	by fulcanelli with IMAP (fetchmail-6.3.26)
	for <debbugs@localhost> (single-drop); Wed, 17 Apr 2019 12:30:05 +0200 (CEST)
Received: from ( [])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by (Postfix) with ESMTPS id E0EEFF60BF9
	for <>; Wed, 17 Apr 2019 12:27:18 +0200 (CEST)
Received: from apollo.hindleynet ([] helo=apollo)
	by with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
	(Exim 4.84_2)
	(envelope-from <>)
	id 1hGhmZ-00024V-Lz; Wed, 17 Apr 2019 11:27:12 +0100
Received: from mark by apollo with local (Exim 4.84_2)
	(envelope-from <>)
	id 1hGhmW-0000ME-A9; Wed, 17 Apr 2019 11:27:08 +0100
Date: Wed, 17 Apr 2019 11:27:08 +0100
From: Mark Hindley <>
To: Dimitris <>
Subject: Re: elogind: doesn't seem to be updating lastlog
Message-ID: <>
References: <155197499736.23377.13231103228601464271.reportbug@emma.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Spam-Status: No, score=-0.0 required=5.0 tests=SPF_PASS autolearn=disabled
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on

On Fri, Mar 08, 2019 at 10:32:02PM +0200, Dimitris wrote:
> On 3/8/19 5:53 PM, Mark Hindley wrote:
> > I have also been struggling to work out where the user login on :0 (above) comes
> > from. With the default install could only reproduce logins on ptys. I eventually
> > managed to do it by adding to the display manager PAM stack in
> > /etc/pam.d/{slim,lightdm}
> > 
> > Had you customised that and it was overwritten in the upgrade at the end of January?
> > 
> no i haven't customised anything in pam.d. not in this install at least.
> not sure either about this login on :0, you're right, it shouldn't be
> there. lastlog should only report tty logins. puzzled about that entry
> too now.
> not having around logs from that time is not helpful, i know..
> anyway, not really sure if this is a bug here. during that period
> (dec-jan) i was testing different scenarios & various DEs, something
> could have triggered that..
> so, feel free to proceed (close?) as you like...


I don't think there is an elogind bug here. I think it is down the the display
manager (slim, lightdm etc) to register logins in lastlog and utmp.

AFAIK lightdm does this already and I have a patch for slim to implement it (see

So closing, as you suggest.



Devuan BTS -- Powered by Debian bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.

Devuan Bugs Owner <>.
Last modified: Fri, 15 Nov 2019 02:35:08 UTC