Home | Devuan | Git | Forum | Packages | Popcon
Donate now!
Download

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

Package: elogind; Maintainer for elogind is Mark Hindley <mark@hindley.org.uk>; Source for elogind is src:elogind.

Reported by: "Dimitris T." <dimitris@stinpriza.org>

Date: Thu, 7 Mar 2019 16:18:01 UTC

Severity: normal

Done: Mark Hindley <mark@hindley.org.uk>

Full log

Message #35 received at 302-done@bugs.devuan.org (full text, mbox, reply):

Received: (at 302-done) by bugs.devuan.org; 17 Apr 2019 10:30:05 +0000
Return-Path: <mark@hindley.org.uk>
Delivered-To: devuanbugs@dyne.org
Received: from tupac3.dyne.org [195.169.149.119]
	by fulcanelli with IMAP (fetchmail-6.3.26)
	for <debbugs@localhost> (single-drop); Wed, 17 Apr 2019 12:30:05 +0200 (CEST)
Received: from mx.hindley.org.uk (mohindley.plus.com [81.174.245.179])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by vm6.ganeti.dyne.org (Postfix) with ESMTPS id E0EEFF60BF9
	for <302-done@bugs.devuan.org>; Wed, 17 Apr 2019 12:27:18 +0200 (CEST)
Received: from apollo.hindleynet ([192.168.1.3] helo=apollo)
	by mx.hindley.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
	(Exim 4.84_2)
	(envelope-from <mark@hindley.org.uk>)
	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 <mark@hindley.org.uk>)
	id 1hGhmW-0000ME-A9; Wed, 17 Apr 2019 11:27:08 +0100
Date: Wed, 17 Apr 2019 11:27:08 +0100
From: Mark Hindley <mark@hindley.org.uk>
To: Dimitris <dimitris@stinpriza.org>
Cc: 302-done@bugs.devuan.org
Subject: Re: elogind: doesn't seem to be updating lastlog
Message-ID: <20190417102708.GP6300@hindley.org.uk>
References: <155197499736.23377.13231103228601464271.reportbug@emma.lan>
 <20190308155308.GC17160@hindley.org.uk>
 <240dddf0-c45e-a5f8-0524-95ba29996234@stinpriza.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <240dddf0-c45e-a5f8-0524-95ba29996234@stinpriza.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Spam-Status: No, score=-0.0 required=5.0 tests=SPF_PASS autolearn=disabled
	version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org

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 pam_lastlog.so 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...

Dimitris,

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
#301)

So closing, as you suggest.

Thanks

Mark

Send a report that this bug log contains spam.

Devuan BTS -- Powered by Debian bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.

Devuan Bugs Owner <owner@bugs.devuan.org>.
Last modified: Sat Apr 20 03:23:21 2024;