https://bugs.kde.org/show_bug.cgi?id=490924
--- Comment #7 from Sophie Dexter <sophie.dexte...@yahoo.co.uk> --- (In reply to Fabian Vogt from comment #6) > You should be able to run the command and try the sleep button. Ha! That was _embarassingly_ obvious :o) Unfortunately it wasn't much help however. I se the testing lockscreen on waking my system which accepted my password first time, followed by the 'real' lockscreen which rejected my password before accepting... Qt logging messages were similar to before. But faking suspend with > It's also possible to "fake" the suspend by removing the call to > PowerManagement::instance()->suspend(); instead of > m_authenticators->cancel(); shows more promise and I see my password being rejected with lockscreen testing. I've tried to annotate logged output, three messages in particular seem to indicate trouble: >> kscreenlocker_greet: Greeter is starting up. >> kscreenlocker_greet: [PAM worker kde-smartcard] start: successfully started >> kscreenlocker_greet: Greeter is running in testing mode >> kscreenlocker_greet: Testing mode enabled: true >> kscreenlocker_greet: [PAM worker kde-fingerprint] start: successfully started >> kscreenlocker_greet: [PAM worker kde] start: successfully started >> Locked at 1722370491 >> kscreenlocker_greet: PamAuthenticators: starting authenticators >> kscreenlocker_greet: PamAuthenticators: state changing from >> PamAuthenticators::Idle to PamAuthenticators::Authenticating >> kscreenlocker_greet: [PAM worker kde] Authenticate: Starting authentication >> kscreenlocker_greet: [PAM worker kde-fingerprint] Authenticate: Starting >> authentication >> kscreenlocker_greet: [PAM worker kde-smartcard] Authenticate: Starting >> authentication >> kscreenlocker_greet: [PAM worker kde-smartcard] Message: Info message: >> auth=authinfo_unavail >> kscreenlocker_greet: PamAuthenticators: Availability changed for >> non-interactive authenticator kde-fingerprint true >> kscreenlocker_greet: [PAM worker kde-smartcard] Authenticate: Authentication >> done, result code: 9 (Authentication service cannot retrieve authentication >> info) >> kscreenlocker_greet: PamAuthenticators: Availability changed for >> non-interactive authenticator kde-smartcard true >> kscreenlocker_greet: PamAuthenticators: Info message from non-interactive >> authenticator kde-smartcard >> kscreenlocker_greet: PamAuthenticators: Availability changed for >> non-interactive authenticator kde-smartcard false >> kscreenlocker_greet: PamAuthenticators: Availability changed for >> non-interactive authenticator kde-smartcard false >> kscreenlocker_greet: [PAM worker kde-fingerprint] Authenticate: >> Authentication done, result code: 9 (Authentication service cannot retrieve >> authentication info) >> kscreenlocker_greet: PamAuthenticators: Availability changed for >> non-interactive authenticator kde-fingerprint false >> kscreenlocker_greet: PamAuthenticators: Availability changed for >> non-interactive authenticator kde-fingerprint false This relates to Password box before pressing (faked) sleep icon >> kscreenlocker_greet: [PAM worker kde] Message: Echo-off prompt: Password: >> kscreenlocker_greet: [PAM worker kde] Starting nested event loop to await >> response >> kscreenlocker_greet: PamAuthenticators: Secret prompt from interactive >> authenticator kde These three messages could be telling >> kscreenlocker_greet: PamAuthenticators: cancelling interactive authenticator >> kscreenlocker_greet: [PAM worker kde] Received cancellation, exiting with >> PAM_CONV_ERR >> kscreenlocker_greet: [PAM worker kde] Nested event loop's exit code was not >> zero, bailing This relates to the failing first password attempt after (faked) resume >> kscreenlocker_greet: [PAM worker kde] Message: Echo-off prompt: Password: >> kscreenlocker_greet: [PAM worker kde] Starting nested event loop to await >> response >> kscreenlocker_greet: PamAuthenticators: Secret prompt from interactive >> authenticator kde >> kscreenlocker_greet: PamAuthenticators: responding to interactive >> authenticator >> kscreenlocker_greet: [PAM worker kde] Received response, exiting nested >> event loop >> kscreenlocker_greet: PamAuthenticators: Interactive authenticator kde >> changed business >> kscreenlocker_greet: [PAM worker kde] Authenticate: Authentication done, >> result code: 7 (Authentication failure) >> kscreenlocker_greet: PamAuthenticators: Interactive authenticator kde >> changed business >> kscreenlocker_greet: PamAuthenticators: Failure from interactive >> authenticator kde >> kscreenlocker_greet: PamAuthenticators: state changing from >> PamAuthenticators::Authenticating to PamAuthenticators::Idle >> kscreenlocker_greet: PamAuthenticators: starting authenticators >> kscreenlocker_greet: PamAuthenticators: state changing from >> PamAuthenticators::Idle to PamAuthenticators::Authenticating >> kscreenlocker_greet: [PAM worker kde] Authenticate: Starting authentication This relates to the 2nd password attempt which succeeds >> kscreenlocker_greet: [PAM worker kde] Message: Echo-off prompt: Password: >> kscreenlocker_greet: [PAM worker kde] Starting nested event loop to await >> response >> kscreenlocker_greet: PamAuthenticators: Secret prompt from interactive >> authenticator kde >> kscreenlocker_greet: PamAuthenticators: responding to interactive >> authenticator >> kscreenlocker_greet: [PAM worker kde] Received response, exiting nested >> event loop >> kscreenlocker_greet: PamAuthenticators: Interactive authenticator kde >> changed business >> kscreenlocker_greet: [PAM worker kde] Authenticate: Authentication done, >> result code: 0 (Success) >> kscreenlocker_greet: PamAuthenticators: Interactive authenticator kde >> changed business >> kscreenlocker_greet: PamAuthenticators: Success from interactive >> authenticator kde >> Unlocked >> Unlocked >> Unlocked >> Unlocked >> Unlocked >> Unlocked >> Unlocked >> Unlocked >> Unlocked -- You are receiving this mail because: You are watching all bug changes.
