Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 738256 - sys-libs/pam(?): console silently fails to log in user and drops back to login screen
Summary: sys-libs/pam(?): console silently fails to log in user and drops back to logi...
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal critical
Assignee: Mikle Kolyada (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-20 19:33 UTC by Dmitri Seletski
Modified: 2020-08-21 07:04 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (file_738256.txt,5.94 KB, text/plain)
2020-08-20 19:33 UTC, Dmitri Seletski
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitri Seletski 2020-08-20 19:33:24 UTC
Created attachment 655794 [details]
emerge --info

trying to log in into console.

Putting username/password.
Log in process does not complain about password. I see cursor for a few seconds and I am dropped to the same log in screen.

After some googling found that this line is offending:
session                required        pam_limits.so
in this file:
/etc/pam.d/system-auth

I commented it, so I am able to log in.
But others perhaps can't.
Prevents boot, IMHO critical priority is justified.
Comment 1 Dmitri Seletski 2020-08-20 19:34:16 UTC
I could log in in 'repair mode', when chosen from GRUB.
Comment 2 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2020-08-21 03:35:53 UTC
Please share: 
* emerge -pvO sys-libs/pam sys-auth/pambase
* Any relevant syslog entries
* whether or not you have run dispatch-conf recently (this is important)

This could be related to pam, pambase, or something else entirely.
Comment 3 Mikle Kolyada (RETIRED) archtester Gentoo Infrastructure gentoo-dev Security 2020-08-21 07:04:22 UTC
pam_limits.so is irrelevant to the login process per se, it may be a problem if only your pam stack is somehow broken, this means you dug up in a wrong direction. I strongly belive that if it were a massive problem people would report it earlier.

I agree with what Sam has already written, plus:

- What are your sys-libs/pam sys-auth/pambase versions?
- What are your use flags for sys-auth/pambase?
- Have you followed this news item if you are a testing branch user [0]?
- Would be nice if you could reproduce the problem and then extract the log that may indicate the problem (say, from chroot) we need /var/log/messages / journalctl -b extraction indicating PAM errors

[0] - https://www.gentoo.org/support/news-items/2020-06-23-upgrade-to-sys-libs_pam-1_4_0.html

Please reopen the bug when all the information gathered. Provided information is not enough to find and solve a problem.