Arch Linux

gen2arch

Member

Registered: 2013-05-16

Posts: 182

SOLVED:Recent update: no longer able to log into KDE after screen lock

Hi

my current setup is: Plasma 5.10.0, Frameworks 5.34.0 and Qt 5.8.0.

When I try to relogin to my session after a screen lock was active sddm (v.0.14.0-2) no longer accepts my password; every attempt to enter it says "login unsuccessful"; I tried with a different keyboard, same thing.

In the journal I see lines like the following:

Jun 04 10:47:14 linux kcheckpass[22714]: pam_tally(kde:auth): Error opening /var/log/faillog for update
Jun 04 10:47:14 linux kcheckpass[22714]: pam_tally(kde:auth): Error opening /var/log/faillog for read

Only way is to open a non graphical konsole and kill the X server.

The sddm I than get accepts the password.

What might that be?

Thanks for your help.

Last edited by gen2arch (2017-06-05 10:20:55)

arojas

Developer

From: Spain

Registered: 2011-10-09

Posts: 2,098

Re: SOLVED:Recent update: no longer able to log into KDE after screen lock

The Plasma screen locker has nothing to do with sddm. Please post the full journal output since locking the screen, the two lines you posted are irrelevant.

gen2arch

Member

Registered: 2013-05-16

Posts: 182

Re: SOLVED:Recent update: no longer able to log into KDE after screen lock

Thanks arojas!

The Plasma screen locker has nothing to do with sddm. Please post the full journal output since locking the screen, the two lines you posted are irrelevant.

Ok, I see, sorry for the confusion, didn't realize that locking is done by plasma itself.

I observed the whole process of failed logins (connected via ssh from a different computer) and looked at the journal via "journalctl -f": unfortunately no messages appear besides the ones already quoted. Especially I don't get the "normal" error, when a wrong passwd is entered:

Jun 04 15:15:00 linux kcheckpass[5601]: pam_tally(kde:auth): Error opening /var/log/faillog for update
Jun 04 15:15:00 linux kcheckpass[5601]: pam_tally(kde:auth): Error opening /var/log/faillog for read
Jun 04 15:15:00 linux unix_chkpwd[5608]: password check failed for user (me)
Jun 04 15:15:00 linux kcheckpass[5601]: pam_unix(kde:auth): authentication failure; logname= uid=1000 euid=1000 tty=:0 ruser= rhost=  user=me
Jun 04 15:15:00 linux kcheckpass[5601]: Authentication failure for me (invoked by uid 1000)

I realized also that the login fails only after a certain  time: if I try to login within a minute or so, it works.

What I can do though to re-log in is the following from plasma's lock screen:

switch user > new session > start new session

I then get the login manager (now lightdm) and upon re-login with my password I find my original unchanged session.

What can I do to further debug this?

Thanks.

arojas

Developer

From: Spain

Registered: 2011-10-09

Posts: 2,098

Re: SOLVED:Recent update: no longer able to log into KDE after screen lock

Possibly related to https://bugs.kde.org/show_bug.cgi?id=380491

arojas

Developer

From: Spain

Registered: 2011-10-09

Posts: 2,098

Re: SOLVED:Recent update: no longer able to log into KDE after screen lock

Please test ksccreenlocker 5.10.0-2

gen2arch

Member

Registered: 2013-05-16

Posts: 182

Re: SOLVED:Recent update: no longer able to log into KDE after screen lock

Please test ksccreenlocker 5.10.0-2

Looks very good: tested a couple of times, after screenlock and resume: no issues! Logging back in succeeded every time.

BTW I had exactly the symptoms described in the kde bug you linked to.

I will keep on trying till tomorrow and then report back.

Thanks

gen2arch

Member

Registered: 2013-05-16

Posts: 182

Re: SOLVED:Recent update: no longer able to log into KDE after screen lock

I consider this as solved: the new version of ksccreenlocker no longer has this problem.

Thanks!

flargen

Member

Registered: 2012-10-27

Posts: 13

Re: SOLVED:Recent update: no longer able to log into KDE after screen lock

I also had this problem, and as a workaround I found that you can login from a TTY and run

loginctl unlock-session cX

where X is the session number found by running

loginctl list-sessions

Starting a new session in SDDM didn't allow me to access my locked session, so I had to do the above.

Last edited by flargen (2017-06-05 17:42:20)