[kde] [Bug 490924] New: The first password attempt is rejected after system wakes from sleep.

[Sophie Dexter]

https://bugs.kde.org/show_bug.cgi?id=490924

            Bug ID: 490924
           Summary: The first password attempt is rejected after system
                    wakes from sleep.
    Classification: I don't know
           Product: kde
           Version: unspecified
          Platform: Fedora RPMs
               URL: https://github.com/sddm/sddm/issues/1941
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: sophie.dexter74 at yahoo.co.uk
  Target Milestone: ---

SUMMARY

The first password attempt is rejected when I resume my system from sleep after
it was put to sleep from the lock screen even though my password appears to be
correct when I make it visible using the show password function. I am always
able to log in on the second attempt. 

My system is unlocked as expected, i.e. without a rejected attempt, when I put
my system to sleep using the application menu launcher's sleep icon or when
unlocking without sleeping.

STEPS TO REPRODUCE
1. Wait for screen to lock automatically after a period of inactivity or lock
with Meta-L key combination
2. Put system to sleep using the Sleep icon on the lock screen
3. Wake system and enter correct password to unlock

OBSERVED RESULT

My password is rejected the first time it is entered, the login screen shakes
and an 'Unlocking failed' message is shown.
I am able to login only when I enter my password a second time.

EXPECTED RESULT

The desktop should be unlocked the first time a correct password is entered.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Fedora 40 - 6.9.10-200.fc40.x86_64
KDE Plasma Version: 6.1.3
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION

I think this may have started when I upgraded my system from Fedora 39 to
Fedora 40, but my journal logs only go back 3 months so I can't be sure, the
oldest record from journalctl output I can find is from shortly after I
upgraded:

May 01 06:32:09 Just4pLeisure kscreenlocker_greet[276611]: pam_unix(kde:auth):
unexpected response from failed conversation function
May 01 06:32:09 Just4pLeisure kscreenlocker_greet[276611]: pam_unix(kde:auth):
conversation failed
May 01 06:32:09 Just4pLeisure kscreenlocker_greet[276611]: pam_unix(kde:auth):
auth could not identify password for [sophie]

The issue persists to this day despite numerous updates to Plasma, Frameworks
and Qt:

Jul 27 17:39:35 Just4pLeisure kscreenlocker_greet[21299]: pam_unix(kde:auth):
unexpected response from failed conversation function
Jul 27 17:39:35 Just4pLeisure kscreenlocker_greet[21299]: pam_unix(kde:auth):
conversation failed
Jul 27 17:39:35 Just4pLeisure kscreenlocker_greet[21299]: pam_unix(kde:auth):
auth could not identify password for [sophie]

Lee Head has submitted a complete journalctl log here
:https://github.com/sddm/sddm/issues/1941#issuecomment-2156369683

Fabian Vogt (Vogtinator) suspects sleeping from the lock screen somehow
triggers a broken PAM conversation:
https://github.com/sddm/sddm/issues/1941#issuecomment-2254224974

I can supply log files as required and would love to try to debug this,
although I may need a bit of guidance...

-- 
You are receiving this mail because:
You are the assignee for the bug.