Bug 359568 - If password checking takes too long, password appears to have been rejected
Summary: If password checking takes too long, password appears to have been rejected
Status: RESOLVED WORKSFORME
Alias: None
Product: kscreenlocker
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Fedora RPMs Linux
: NOR minor
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-19 11:37 UTC by Robin Green
Modified: 2020-12-22 04:34 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robin Green 2016-02-19 11:37:50 UTC
If password checking takes too long, the UI behaves as if the password has been rejected - but then it unlocks the screen.
Comment 1 Martin Flöser 2016-02-19 12:46:11 UTC
do you get a password failed message?

It's intended behavior to block the UI from further input while the password is being checked. That is the input field gets disabled and only re-enable once the password is evaluated.
Comment 2 Robin Green 2016-02-19 13:27:34 UTC
No, no password failed message. But I don't think I ever get a password failed message anyway.
Comment 3 Martin Flöser 2016-02-19 14:49:48 UTC
sorry, but this looks like intended behavior:
https://quickgit.kde.org/?p=plasma-workspace.git&a=blob&h=03ac02149ca8c7db133c42aa39fd7f9d946dda51&hb=a56f6c9d98197541663713978d5a754fa667a15a&f=lookandfeel%2Fcontents%2Flockscreen%2FMainBlock.qml#l99

While the password gets verified the input field is disabled and after a timeout of 3 sec the password field is cleared and enabled again.

I don't see a bug there. The better question is: why does checking the password takes so long in your case that it hits the boundaries of the safe guards?
Comment 4 Justin Zobel 2020-11-22 00:51:13 UTC
Robin, can you please check if this issue is still occurring. If so, are you able to provide the information requested in Comment 3, thank you.
Comment 5 Bug Janitor Service 2020-12-07 04:34:04 UTC
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!
Comment 6 Bug Janitor Service 2020-12-22 04:34:53 UTC
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!