Summary: | Can't unlock the screen if the user has an empty password | ||
---|---|---|---|
Product: | [Plasma] kscreenlocker | Reporter: | Graham Perrin <grahamperrin> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | critical | CC: | andrej, bhush94, kde, nate, palmadaniel196, thuryn1 |
Priority: | VHI | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | FreeBSD | ||
Latest Commit: | https://invent.kde.org/plasma/plasma-workspace/commit/dc6341bb3073ebe0beb945018cc7bb67ee2dd828 | Version Fixed In: | 5.25 |
Sentry Crash Report: |
Description
Graham Perrin
2021-07-20 03:08:12 UTC
*** Bug 440344 has been marked as a duplicate of this bug. *** Eek. Can confirm. Does SDDM have an impact? For example: Passwordless Login · Issue #751 · sddm/sddm <https://github.com/sddm/sddm/issues/751> The behaviour is now changed - but not perfect (hence leaving this open) it now unlocks immediately on resume from the "screensaver" mode. Git commit dc6341bb3073ebe0beb945018cc7bb67ee2dd828 by David Edmundson. Committed on 18/05/2022 at 11:09. Pushed by davidedmundson into branch 'master'. Add an explicit unlock button for passwordless users In the refactor we correctly made it so passwordless users were not prompted for passwords. This is in the right direction but the UX was still slightly off as it meant wiggling the mouse unlocked the screen, not an explicit action. This patch adds an explicit button that must be pressed if no other prompts were given during the authentication process. M +10 -1 lookandfeel/contents/lockscreen/LockScreenUi.qml A +23 -0 lookandfeel/contents/lockscreen/NoPasswordUnlock.qml [License: GPL(v2.0+)] https://invent.kde.org/plasma/plasma-workspace/commit/dc6341bb3073ebe0beb945018cc7bb67ee2dd828 Solution of this bug is not good. I use Howdy for face unlocking and it worked fine before. I get annoying screen with Unlock button now. Moreover, if I connect second screen I get second screen with Unclock button. So it would be great to revert this change. The first issue is Bug 454706, and the second issue should be fixed with Plasma 5.25.3.1. If it's not, please file a new bug report. |