Bug 396191 - Screen locker does not communicate kcheckpass failure
Summary: Screen locker does not communicate kcheckpass failure
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kscreenlocker
Classification: Plasma
Component: greeter (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-05 09:35 UTC by Kai Uwe Broulik
Modified: 2022-11-03 16:24 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kai Uwe Broulik 2018-07-05 09:35:06 UTC
When the underlying authentication service breaks (e.g. network connection loss for ldap login), there is no indication to the user other than "Unlocking failed".

Plasma 4's lock screen would at least show "Authentication failed because the underlying service isn't working correctly" (or something like this) so you at least knew you weren't mistyping your password 10 times in a row.

In ConvPutAuthError it probably should emit error with a message instead of just emitting failed
Comment 1 Unknown 2020-12-31 10:02:09 UTC
Any progress on this?
Comment 2 Nate Graham 2022-11-03 16:24:43 UTC
kcheckpass support was removed a few releases ago; closing.