From: LinArcX <LinArcX@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Couldn't login from console after update.
Date: Sat, 12 Aug 2023 14:05:43 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45562@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]
New issue by LinArcX on void-packages repository
https://github.com/void-linux/void-packages/issues/45562
Description:
### Is this a new report?
Yes
### System Info
Void 6.1.30_1 x86_64 GenuineIntel uptodate hold rFF
### Package(s) Affected
pam, pam-base
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
I should log in without any issues.
### Actual behaviour
couldn't log in until i chrooted and commented:
`session required pam_lastlog.so silent`
in:
`/etc/pam.d/system-login`
### Steps to reproduce
update your system.
Try to log in again via the console. you can't. the reason is that this line:
`session required pam_lastlog.so silent`
is not commented in this file: `/etc/pam.d/system-login`
It is worth mentioning that pam-base was also installed on my machine.
I saw this post on the void website: (written in 2020)
https://voidlinux.org/news/2020/12/pam-1.5.1.html
But it's interesting that I faced this issue in 2023!
next reply other threads:[~2023-08-12 12:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 12:05 LinArcX [this message]
2023-08-12 14:04 ` leahneukirchen
2023-08-12 14:13 ` LinArcX
2023-08-12 14:54 ` leahneukirchen
2023-08-12 14:58 ` [ISSUE] [CLOSED] " leahneukirchen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45562@inbox.vuxu.org \
--to=linarcx@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).