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

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

View this report as an mbox folder.


Information forwarded to devuan-bugs@lists.dyne.org, owner@bugs.devuan.org:
bug#302; Package elogind. Full text available.



Message sent to devuan-bugs@lists.dyne.org, owner@bugs.devuan.org:

Subject: bug#302: elogind: doesn't seem to be updating lastlog
To: Mark Hindley <mark@hindley.org.uk>
From: Dimitris <dimitris@stinpriza.org>
Date: Fri, 8 Mar 2019 22:32:02 +0200

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--fuIQrzgsds6NhgwMdxoVe3uzkwtBiTA79
Content-Type: multipart/mixed; boundary="Ig1TpswPew3PKlgoRg2mWGWMEkmACQsV5";
 protected-headers="v1"
From: Dimitris <dimitris@stinpriza.org>
To: Mark Hindley <mark@hindley.org.uk>
Cc: 302@bugs.devuan.org
Message-ID: <240dddf0-c45e-a5f8-0524-95ba29996234@stinpriza.org>
Subject: Re: elogind: doesn't seem to be updating lastlog
References: <155197499736.23377.13231103228601464271.reportbug@emma.lan>
 <20190308155308.GC17160@hindley.org.uk>
In-Reply-To: <20190308155308.GC17160@hindley.org.uk>

--Ig1TpswPew3PKlgoRg2mWGWMEkmACQsV5
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 3/8/19 5:53 PM, Mark Hindley wrote:
> I have also been struggling to work out where the user login on :0 (abo=
ve) comes
> from. With the default install could only reproduce logins on ptys. I e=
ventually
> managed to do it by adding pam_lastlog.so to the display manager PAM st=
ack in
> /etc/pam.d/{slim,lightdm}
>=20
> Had you customised that and it was overwritten in the upgrade at the en=
d of January?
>=20

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

thanks,
d.



--Ig1TpswPew3PKlgoRg2mWGWMEkmACQsV5--

--fuIQrzgsds6NhgwMdxoVe3uzkwtBiTA79
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQGzBAEBCgAdFiEEddlu1gom7sXWP9ZRvUcY7+WkADkFAlyC0UIACgkQvUcY7+Wk
ADlq6Av/bE/Rlmr1QkphACNZeJleCAi16Dwb7G6e/lZNTrtVJ4WlIHJxAPhpPdTM
OJUOow9xxd8jPASUISV1r9dnqIkWEkqz6nkKO3S1bJC0I3xe2hAh1dGTbuql5LF0
WhbbNV+9qNc8oexaUFWTSYuLk00nZISUeEpBp9tl+NI6al6ZkHuCejhuO75TQMq2
R/AAPB/zTtjjp4Gju0vwvFYtRAy90N2/hVD2ollHVXkdHTGr+OSLxZxdwMkXWyQh
KtpUwRKf4ds+TQUAdeACMTi8EmMD3Z+fBRq3NJZlz5/9G1oKYowaLfgLlBnBU3ac
pdakYqMJu+X5y4iyg7ldv1aCkbRmtpm2+VSWsjoymF/TsO0GsJdbCxY1UynUM2An
Kj/uFn3D6pRyp1oBTWSbLd2p6xn7UFuMSgfCqLnW/TjMB3/gxANfR6Wy/z/vT0gJ
JY6LEA7aLkAyRMAp5NCaCwTxyIxjqV1pyS+VpjFvkhdsxBWJDDHyD7QPVM1rLTvA
QQMbEn2J
=SXyM
-----END PGP SIGNATURE-----

--fuIQrzgsds6NhgwMdxoVe3uzkwtBiTA79--





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 <owner@bugs.devuan.org>.
Last modified: Mon, 18 Nov 2019 07:43:26 UTC