Devuan bug report logs -
#302
elogind: doesn't seem to be updating lastlog
Full log
🔗
View this message in rfc822 format
Your message dated Wed, 17 Apr 2019 11:27:08 +0100
with message-id <20190417102708.GP6300@hindley.org.uk>
and subject line elogind: doesn't seem to be updating lastlog
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Devuan Bugs Owner
(administrator, Devuan bugs database)
--------------------------------------
Received: (at submit) by bugs.devuan.org; 7 Mar 2019 16:10:02 +0000
Return-Path: <dimitris@stinpriza.org>
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); Thu, 07 Mar 2019 17:10:02 +0100 (CET)
Received: from cacofonix.stinpriza.org (cacofonix.stinpriza.org [148.251.45.81])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by vm6.ganeti.dyne.org (Postfix) with ESMTPS id 7D26DF60B6E
for <submit@bugs.devuan.org>; Thu, 7 Mar 2019 17:09:41 +0100 (CET)
Authentication-Results: vm6.ganeti.dyne.org;
dkim=pass (2048-bit key; unprotected) header.d=stinpriza.org header.i=@stinpriza.org header.b="qP39ctcB";
dkim-atps=neutral
Received: from emma.lan (178-183-199.dynamic.cyta.gr [178.59.183.199])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by cacofonix.stinpriza.org (Postfix) with ESMTPSA id 8068C2B0179F;
Thu, 7 Mar 2019 18:09:39 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=stinpriza.org; s=mail;
t=1551974980; bh=zIfVbRVixUHwqLpJFADxuJK3KKIbYcV+aJDY4YMW74s=;
h=From:To:Subject:Date:From;
b=qP39ctcBhDb966bR8j6T9mlvk/yfPe6lTTjER55uaZqGx9NiCkihh6b5AK4f3mPe4
Tgzxq89aSqV8KyNwbaCr5tykkIgopQOJMMYsh6rgyjnwXy1jF8yvHq93772sHjyCtF
Fgs8PleGhASC167vCTMPadipFP2+Jc8OG1JqN/d4nUcGAfSzhWUEGC49E7iQ0yIyr+
3YwDaWXJLt/3+J9+wgXeNsll9m8UZGPZkj4pCdUi3PmLYxe67IUSIj+1/+sYRfYqrG
NZw5AOz0oRI7H9+gKrphLSzB7M4P3sZlhCwxzTkNacwVNK71yM319sGQB3IH3Pk4DM
YTLEgoHLDcioA==
Received: by emma.lan (sSMTP sendmail emulation); Thu, 07 Mar 2019 18:09:57 +0200
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Dimitris T." <dimitris@stinpriza.org>
To: Devuan Bug Tracking System <submit@bugs.devuan.org>
Subject: elogind: doesn't seem to be updating lastlog
Message-ID: <155197499736.23377.13231103228601464271.reportbug@emma.lan>
X-Mailer: reportbug 7.5.1+devuan1
Date: Thu, 07 Mar 2019 18:09:57 +0200
X-Virus-Scanned: clamav-milter 0.100.2 at cacofonix.stinpriza.org
X-Virus-Status: Clean
X-Spam-Status: No, score=-0.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,SPF_PASS
autolearn=disabled version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org
Package: elogind
Version: 239.3+20190131-1
Severity: normal
since 30/1 lastlog doesn't seem to be updated for display manager logins. tty logins are reported correctly as seen below :
# lastlog
Username Port From Latest
root tty1 Thu Mar 7 10:49:55
user :0 Wed Jan 30 15:36:23
31/1 was the policykit update ( https://lists.dyne.org/lurker/message/20190131.103118.c6fc512b.en.html ), maybe related to that(?).
thanks,
d
-- System Information:
Distributor ID: Devuan
Description: Devuan GNU/Linux beowulf/ceres
Release: 10
Codename: n/a
Architecture: x86_64
Kernel: Linux 4.19.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
Versions of packages elogind depends on:
ii dbus 1.12.12-1
ii debconf 1.5.71
ii libacl1 2.2.53-4
ii libc6 2.28-8
ii libelogind0 239.3+20190131-1
ii libselinux1 2.8-1+b1
pn libudev1 <none>
ii lsb-base 10.2018112800
Versions of packages elogind recommends:
ii policykit-1 0.105-25+devuan1
elogind suggests no packages.
-- no debconf information
---------------------------------------
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.