SUMMARY *** my Fedora is configured to use PIN (OTP via Android google auth), on Linux side it is done via package "google-authenticator-1.09-3.fc35.x86_64" and in PAM configured via password-auth : auth required pam_google_authenticator.so nullok PROBLEM: When screen is locked and I want to unlock it there's only field to enter password but not field to enter PIN first, evry unlock attempt thus leads to fail I had to delete whole kscreenlock* stuff by force and replace it by xscreensaver that SUPPORTS entering PIN+password ! Also kdm and sddm do NOT provide PIN support thus i had to replace it by lightdm which DOES *** STEPS TO REPRODUCE 1. lock screen manually or by inactivity 2. screen is locked 3. lock screen does NOT provide ANY way to enter PIN 4. unlock ALWAYS fails EXPECTED RESULT sddm/kdm and screenlocker shall contain additional field for entering OTP/PIN SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 35 KDE Plasma Version: rpm -qa | grep kscreenlo kscreenlocker-5.23.2-1.fc35.x86_64 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Thank you for reporting this issue in KDE software. As it has been a while since it was reported, can we please ask you to see if you can reproduce the issue with a recent software version? Like Plasma 5.25, or ideally 5.26? I ask because 5.25 contained some PAM changes that could have fixed this. Can you check? If you can still reproduce the issue with 5.25 or later, please change the status to "CONFIRMED" when replying. Thank you!
Hello I checked in my Fed.35 kscreenlocker-5.25.4-1.fc35.x86_64 plasma-workspace-common-5.25.4-1.fc35.x86_64 and yes u r correct unlocking from screenlocker works now. I didnt notice it as it is very badly visually implemented, there is no any mention(no text/editbox) about separate entering PIN and later on password. There's only "editbox" enter password.... I need to enter PIN 1st, press ENTER, then delete editbox content, type password and ENTER....Thats confusing... Other screenlockers i found some time ago ask separately about PIN and then password Can this be improved ? Thank you. BR, raven4 On 04. 11. 22 22:21, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=445769 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |nate@kde.org > Status|REPORTED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Nate Graham <nate@kde.org> --- > Thank you for reporting this issue in KDE software. As it has been a while > since it was reported, can we please ask you to see if you can reproduce the > issue with a recent software version? Like Plasma 5.25, or ideally 5.26? I ask > because 5.25 contained some PAM changes that could have fixed this. > > Can you check? If you can still reproduce the issue with 5.25 or later, please > change the status to "CONFIRMED" when replying. Thank you! >
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!