I am having an issue with my Ubuntu 16.04 distribution. What is happening is I'll lock my terminal to perform some small task or take a break from my work, but occasionally when I return, I will attempt to sign in but will be told my password is wrong. After several attempts, I end up having to restart my machine.

Does anyone know what is going on (no I am not typing it wrong 3 times in a row or using the wrong password)? If this happens is there a way to get in without having to do a hard restart?

Some possible solutions at the link below at 'askubuntu'.

http://askubuntu.com/questions/50983...d-ubuntu-14-04

.
Where correct $USER and $PASSWD are entered in the X login window as you have assuredly stated above, the problem is sometimes owed to the resource sockets permission. There are two (2) simple practical ways to solve this:

1 - Simply keep on repeating the login $USERNAME and $PASSWD. To my experience when repeating reaches the 4th or 5th time the socket gives up taking the user and passwd at its face value, and let's you in, ignoring other issues. or,

2 - Ctl+Alt+F3, login at the shell then remove the ailing sockets then return to the X login window Ctl-Alt+F7(or F8) there login as normally. You should be allowed this time.

Don't worry about sockets removed, X creates them voluntarily at run time when there is none that exist.

Hope that helps. Good luck.

m.m.

1 members found this post helpful.

I've found thyat the X-server sometimes uses a slightly different keyboard mapping after it is launched, and if you log out and try to log back in then some of the keystrokes might be incorrect. You can test it by CTRL+ALT+F1 and type out your password in the terminal. You can also try to log in to the terminal. One of the catchall commands for systemd errors is:

$ dpkg-reconfigure libpam-systemd

Because systemd uses pam and screws it up a lot.