https://bugs.kde.org/show_bug.cgi?id=490924
--- Comment #24 from Sophie Dexter <sophie.dexte...@yahoo.co.uk> --- (In reply to Fabian Vogt from comment #23) > (In reply to Sophie Dexter from comment #19) > > (In reply to Fabian Vogt from comment #18) > > > I used 'sudo vi /etc/authselect/password-auth' when editing, unsure what I > > > was supposed to do/see with the root shell though,? > > > > The (extra) open root shell would have enabled you to use it to fix the PAM > > configuration in case you made a mistake, making you unable to login. > > Exactly that! password-auth is likely used by all authentication methods > (tty + graphical login, ssh), so if there's a typo or other issue you'd lock > yourself out of your system. Understood! - I did have a TTY3 session logged in with my normal user account but I now realise that may not have been enough if I needed root access but had 'broken' my PAM configuration. Thank you both for explaining :-) (In reply to Fabian Vogt from comment #23) > (In reply to Sophie Dexter from comment #19) > > (In reply to Fabian Vogt from comment #18) > > > The fix would be to return PAM_CONV_ERR until pam_authenticate returns > > > failure. > > Great!, umm, how :?: > > Like this: https://invent.kde.org/plasma/kscreenlocker/-/merge_requests/240 > Can you please check whether this MR fixes the issue for you? > Unfortunately not really, but behaviour is different: The lock screen almost works with authselect 'local' profile with the peculiarity that the lock screen shakes and informs 'Unlocking Failed' then sleeps after that message's timeout expires. However, with authselect's 'sssd' profile I have to press the sleep button twice before my system will sleep. I see the screen shake and an 'Unlocking Failed' message each time I press sleep. The better news is that unlocking works at the first attempt with either profile. the plot thickens... -- You are receiving this mail because: You are watching all bug changes.
