Authorization failed on locked screen [Solved]

[linuxfluesterer]

Hallo guys.
I had to make a brand new installation on a new SSD. For this I used weekend's Daily-Build with latest Plasma elements, version 5.12.3 and Kernel 4.14. Installation went easy. But when I started to work with the installed Sabayon on SSD now, then I have a severe problem.
- First I boot into login screen, I can enter my password and the Plasma DE is ready to use
- After a while (5 minutes) the screen is locked, so far, so good
- I am asked for my password to unlock again, but after entering my password, I always receive the message:

Code: Select all

Authorization failed

The only way to my locked Plasma session ist the following
1. Change the terminal by pressing <Ctrl-Alt-F2>
2. Login as root
3. Enter the following command to find out which session is my Plasma:

Code: Select all

loginctl list-session
SESSION UID  USER             SEAT             TTY
1       1000 linuxfluesterer  seat0
2          0 root             seat0            /dev/tty2       

then I get a list with root and my own session (1000)
4. to unlock my session then I type:

Code: Select all

loginctl unlog-session 1

(my session has id no. 2)
5. Then I have to press <Ctrl-Alt_F1>
and my Plasma session is unlocked again ... but, this is not the way to solve Authorization failed

So, what is wrong with the login manager, or which program ever handles my username and my password for locked sessions?

Thank you in advance.

-Linuxfluesterer (I love KDE...)

[Stupot]

viewtopic.php?f=53&t=33995#p181195

[linuxfluesterer]

viewtopic.php?f=53&t=33995#p181195

Thank you very, very much, Stupot and to Andy (anomaly65) also. I have searched for the keywords "Authorization failed", so I did not receive this solution in forum's topics.

However, I don't know, what is the reason, why this directory:

Code: Select all

/usr/lib64/libexec/kcheckpass

is not set with 's' by default after fresh install.
I will remember this solution and write it into a to do list for a future install.
Of course, I will mark this thread as [Solved] now.

-Linuxfluesterer (I love KDE...)

[linuxfluesterer]

************************* Update ********************************
After upgrading my system to Plasma 5.12.4 (and other components) today, the same problem appears. It is no more possible to login on a locked screen. Something in the upgrade must reset the flag for:

Code: Select all

/usr/lib64/libexec/kcheckpass

The solution is still to enter:

Code: Select all

chmod u+s /usr/lib64/libexec/kcheckpass

as root again. Then it works to relogin.

-Linuxfluesterer (I love KDE...)

[sabayonino]

Something in the upgrade must reset the flag for:

Code: Select all

/usr/lib64/libexec/kcheckpass

Simply the upgrade overwritten this libraries

as dirty fix you can add to the root .bashrc

Code: Select all

chmod u+s /usr/lib64/libexec/kcheckpass

Code: Select all

# echo "chmod u+s /usr/lib64/libexec/kcheckpass" >> /root/.bashrc"

or to the root cronjob

Code: Select all

# crontab -e

add

Code: Select all

@reboot  chmod u+s /usr/lib64/libexec/kcheckpass

reinstall kde-plasma/kscreenlocker package and check if it works after reboot/and locker

[edit] I've no problem with kde screen locker . I can relogin to my kde session

[linuxfluesterer]

Thanks Sabayonino.
Ok, I can make a separate task for crontab.
I decided to set the flag while booting, while I'm executing quite a 'local.d' adopted for systemd. I have several things to do before I want to have shown the login screen. But the way with put a line in root's .bashrc seems to be too late in case of fail.
Well, I need to think about, when I update again a part of Plasma.

-Linuxfluesterer (I love KDE...)

[Stupot]

I still run into this problem with every KDE upgrade (I didn't do the cron job, assuming this was going to be fixed by upstream at some point).

[joost]

I never run into this problem myself. You guys use SDDM? I switched to lightdm some time ago. (KDE images are also shipping with that now)

[Stupot]

I am using SDDM on both of my systems. Although does the DM actually come into play for KDE's lock screen?