* [ISSUE] Couldn't login from console after update.
@ 2023-08-12 12:05 LinArcX
2023-08-12 14:04 ` leahneukirchen
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: LinArcX @ 2023-08-12 12:05 UTC (permalink / raw)
To: ml
[-- 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!
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Couldn't login from console after update.
2023-08-12 12:05 [ISSUE] Couldn't login from console after update LinArcX
@ 2023-08-12 14:04 ` leahneukirchen
2023-08-12 14:13 ` LinArcX
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: leahneukirchen @ 2023-08-12 14:04 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 210 bytes --]
New comment by leahneukirchen on void-packages repository
https://github.com/void-linux/void-packages/issues/45562#issuecomment-1675929837
Comment:
You claim to use glibc, there pam_lastlog should work fine?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Couldn't login from console after update.
2023-08-12 12:05 [ISSUE] Couldn't login from console after update LinArcX
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
3 siblings, 0 replies; 5+ messages in thread
From: LinArcX @ 2023-08-12 14:13 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 249 bytes --]
New comment by LinArcX on void-packages repository
https://github.com/void-linux/void-packages/issues/45562#issuecomment-1675934504
Comment:
yes i'm using glibc. no, i couldn't login. until i manually updated that file and commented pam_lastlog.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Couldn't login from console after update.
2023-08-12 12:05 [ISSUE] Couldn't login from console after update LinArcX
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
3 siblings, 0 replies; 5+ messages in thread
From: leahneukirchen @ 2023-08-12 14:54 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 207 bytes --]
New comment by leahneukirchen on void-packages repository
https://github.com/void-linux/void-packages/issues/45562#issuecomment-1675950719
Comment:
Sorry, can reproduce on pam 1.5.3_1. Will be fixed soon!
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [ISSUE] [CLOSED] Couldn't login from console after update.
2023-08-12 12:05 [ISSUE] Couldn't login from console after update LinArcX
` (2 preceding siblings ...)
2023-08-12 14:54 ` leahneukirchen
@ 2023-08-12 14:58 ` leahneukirchen
3 siblings, 0 replies; 5+ messages in thread
From: leahneukirchen @ 2023-08-12 14:58 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]
Closed 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!
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2023-08-12 14:58 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-08-12 12:05 [ISSUE] Couldn't login from console after update LinArcX
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
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).