So when I come back after away from my pc for a long time (3 or 4 hours), it shows “the session is locked by user1(me)”. When I input the password, it shows “can’t log in due to authentication failure”.
This happens if I afk for a long time (3 or 4 hours) and the screen was locked by a screen saver.
I had this problem since version 12.3.
It seemed I can’t do nothing but press the power button when this happens.
I am not sure if it happens every time, because most of the time I can log in from a locked screen.
On 2014-01-14 16:16, bonedriven wrote:
>
> So when I come back after away from my pc for a long time (3 or 4
> hours), it shows “the session is locked by user1(me)”. When I input the
> password, it shows “can’t log in due to authentication failure”.
Try setting up a different password.
> 2. I had this problem since version 12.3.
> 3. It seemed I can’t do nothing but press the power button when this
> happens.
You probably can enter [Ctrl][Alt][F1], log in as your user, and try
killing the screensaver. Use [Ctrl][Alt][F7] to go back to the graphical
session.
As worst, you can do:
su -
init 3
init 5
which kills and reinits the graphical session.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
Not good to press the power button, but you’ll probably know this.
Somewhere in the SUSE menu (click on the head of the chameleon in the lower left corner of the screen, I’m using KDE),
under applications, you can choose sth. like system preferences to set the time after which your session is locked.
Otherwise try with YaST.
There you should as well be able to completely disable the locking of the session (that’s what I did for several consecutive
versions of openSUSE already).
He meant ‘caps lock’.
Funny little typing error
Yes, if you have caps lock on, an didn’t recognize that, your password may never work unless you
disable caps lock again.
Yes, pressing [Ctrl][Alt][F1] gives you the opportunity to login to a console,
but then you could as well immediately login as root (user name ‘root’).
After that I would prefer a
shutdown -h now
Then you can decide if you want to start the PC again immediately, or later.
I have seen the state of that change at times when locking out.
Also, I find that occasionally the login from the lock screen does not respond to typing from the keyboard, so I can’t enter my password, but if I hit enter, it gives me a login error, then the chance to try again. It works properly on the next attempt.
That is an odd error message, can’t remember ever seeing it before. Almost sounds as if the screen locker can’t talk to the authentication back-end…
Have you tried looking in .xsession-errors or .xsessions-errors-:0 in your home directory? Any errors in there that might shed some light on what’s going on?
Or perhaps /var/log/messages? Does that log any authentication problems?
Thank you for the tips.
In .xsession-errors-:0 it is a mess of error messages without time stamp, while in /var/log/messages I don’t know if the “authentication failure” message is for the wrong password or the “authentication failed to work”.
I’ll have to check that again next time when it happens.
BTW, what should I do to check if a hard reboot has done some damage to the system? As windows would do a disk check after a hard reboot.
I believe (not 100% sure) that .xsession-errors-:0 is for the current session, so reading from the bottom upwards, may yield some interesting results. In /var/log/messages, you should see an “authentication failure” for an incorrect password. Any other message could give a clue.
It is normal for filesystems to be checked upon boot, and most errors (most likely orphaned stuff) get corrected automatically if the volume was not cleanly unmounted.
