See https://microos.opensuse.org/blog/2023-09-28-replace-utmp-with-logind/ and so on. >=pam-1.5.1 has --{enable,disable}-logind for its lastlog module. We currently pass --disable-logind as it doesn't have elogind support yet.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c8e05f732a617ecfe7a5e875ebb044074f58b386 commit c8e05f732a617ecfe7a5e875ebb044074f58b386 Author: Sam James <sam@gentoo.org> AuthorDate: 2024-05-03 08:12:46 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-05-03 08:12:53 +0000 sys-libs/pam: add bug ref for elogind TODO Bug: https://bugs.gentoo.org/931115 Signed-off-by: Sam James <sam@gentoo.org> sys-libs/pam/pam-1.5.3-r1.ebuild | 2 +- sys-libs/pam/pam-1.5.3.ebuild | 2 +- sys-libs/pam/pam-1.6.1.ebuild | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
I was wrong at first: lastlog is deprecated, and replaced by a logind-backed module. We currently enable lastlog temporarily until we get elogind support sorted. Quoting 1.5.3 release notes: """ Deprecated pam_lastlog: this module is no longer built by default because it uses utmp, wtmp, btmp and lastlog, but none of them are Y2038 safe, even on 64bit architectures. pam_lastlog will be removed in one of the next releases, consider using pam_lastlog2 (from https://github.com/thkukuk/lastlog2) and/or pam_wtmpdb (from https://github.com/thkukuk/wtmpdb) instead. """
