| Summary: | w\ fingerprint unlocking enabled: Black screen and cursor for 30 seconds after cancelling screen locking within the "unlock w/o password" grace period | ||
|---|---|---|---|
| Product: | [Unmaintained] kscreenlocker | Reporter: | postix <postix> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 5.27.9 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=465266 | ||
| Latest Commit: | https://invent.kde.org/plasma/plasma-workspace/-/commit/2be90db50bd369d44a567e3642ec98deca21187c | Version Fixed/Implemented In: | |
| Sentry Crash Report: | |||
|
Description
postix
2023-11-21 12:31:09 UTC
I reference bug #465266 as it sounds related but there no one reports a black screen. This issue seems to be related to fingerprint unlocking, as I can short cut the black screen by putting my finger on the fingerprint reader and the last four lines of the log posted in the opening post, namely ``` kscreenlocker_greet: pam_unix(kde:auth): unexpected response from failed conversation function kscreenlocker_greet: QEventLoop: Cannot be used without QApplication kscreenlocker_greet: pam_unix(kde:auth): conversation failed kscreenlocker_greet: pam_unix(kde:auth): auth could not identify password for [user] ``` do not appear in journalctl. IIRC there's a 30 seconds timeout for the fingerprint reader, which would perfectly correlate. Maybe this issue is fixed in 6.0 where multiple PAM can be used simultaneously but I don't have the time to test this. A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3610 Git commit 2be90db50bd369d44a567e3642ec98deca21187c by David Edmundson. Committed on 28/11/2023 at 11:50. Pushed by davidedmundson into branch 'master'. Fix most of the lock screen The commit introduced the idea of tying the UI to the authentication state. Starting and cancelling as the UI became visible. Whilst nice on paper this had two critical bugs: - cancelling an interactive authentication leads to an entry in the faillock list. This means pressing escape 3 times in quick successsion could lock you out your account for 10 minutes. - There was a concept of a failed state, which wasn't handled in the UI properly leading to prompts disappearing. The notification about the failed lock could not be seen. It also failed to handle the prompts correctly, we had multiple things bound to the same root.notification completely ignoring the handleMessage function which is trying to stack messages. This reverts some of commit 59cdc995e738a0b1cd734e2d1be19e87db99f32b, but keeps the core feature. Related: bug 465266 M +2 -0 lookandfeel/components/WallpaperFader.qml M +22 -17 lookandfeel/org.kde.breeze/contents/lockscreen/LockScreenUi.qml https://invent.kde.org/plasma/plasma-workspace/-/commit/2be90db50bd369d44a567e3642ec98deca21187c |