Bug 454708 - 8dbec4a153be35bcab4a1877ee524a7cbcb72e84 causes the UI to not appear immediately when using fingerprint auth
Summary: 8dbec4a153be35bcab4a1877ee524a7cbcb72e84 causes the UI to not appear immediat...
Status: RESOLVED FIXED
Alias: None
Product: kscreenlocker
Classification: Unmaintained
Component: greeter (other bugs)
Version First Reported In: 5.24.90
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: regression, usability
Depends on:
Blocks:
 
Reported: 2022-06-01 15:28 UTC by Nate Graham
Modified: 2022-06-16 19:14 UTC (History)
1 user (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Nate Graham 2022-06-01 15:28:10 UTC 
Before 8dbec4a153be35bcab4a1877ee524a7cbcb72e84, when using fingerprint auth, the UI appeared immediately when the lock screen became visible. This allowed you to simply put your finger on the reader immediately to unlock.

8dbec4a153be35bcab4a1877ee524a7cbcb72e84 changes it so that now the UI only appears when you hit a key or wiggle the mouse, both of which are unnecessary when using fingerprint auth.

This is a regression from 5.24, when the UI appeared immediately when using fingerprint auth.
Comment 1 Nate Graham 2022-06-16 19:14:28 UTC 
Cannot reproduce anymore.