#Cannot Login as User
1 messages · Page 1 of 1 (latest)
Please follow the Standard Litany when asking a question:
• What was your environment? What was your operating system, configuration?
• What did you do? What did you run or test? Where?
• What actually happened? What were the exact results, complete log contents, exact error messages?
• What did you expect? What were you aiming to achieve? What result were you looking for?
Vague or superficial questions will yield vague or superficial answers. False information leads to false solutions.
I did find a thread that might help you but I do need a bit more info
- OS: EndeavourOS, With latest Gnome updates and kernel
- I basically used my pc for discord/internet browsing
- How do I get logs?
normally running journalctl there's a few flags you can pass on to it
I tried journalctl but there's too much going on
try this journalctl -xe | grep "authentication failure"
assuming that is the proper error
you can change the "authentication failure" to what ever the error was
the "CONTENTS HERE" is just a pattern that grep looks for, that can be whatever you need it to be
sorry for the caps
okay I think I got the error log
if you don't remember if it was lower case or not then change the grep to grep -i "search pattern here"
@desert summit do you have a /etc/gdm/custom.conf file?
we need to add a debug section, from all my reading it's looking like PAM is the failure point
you can make it
is there a command for that
do you have nano, nvim vim?
it should look like
[debug]
Enable=true
alright
reboot
okei done
the logs should be located in /var/log/messages per that link I included above
should they be long in nature, you can use
.s rs
<command to print output> |& curl --data-binary @- https://paste.rs
when you cat the logs
use the same journalctl command from above but grep gdm pass in the -i flag though so it grabs GDM too just in case
those are the actual Gnome docs so I have nothing for you in that case
journalctl -xe _COMM=gdm apparently also work, never tried that myself so
theres
gkr-pam: unable to locate daemon control file
gkr-pam: stashed password to try later in open session
and
dbus-daemon: [system] Activating via systemd: service name='org.freedesktop.home1 unit='dbus-org.freedesktop.home1.service" requested by ':1.62`
then the log ends
lol duh, I forgot to tell you to make sure the login fails