https://bugs.kde.org/show_bug.cgi?id=456210
Harald Sitter <sit...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
|ma/kscreenlocker/commit/a92 |ma/kscreenlocker/commit/161
|73c87e8582be7aa1e3de14d92b8 |f9d4c5151e4f3871e670531883b
|0ec92c4f44 |cb6a198d1f
--- Comment #82 from Harald Sitter <sit...@kde.org> ---
Git commit 161f9d4c5151e4f3871e670531883bcb6a198d1f by Harald Sitter.
Committed on 26/04/2023 at 11:31.
Pushed by sitter into branch 'Plasma/5.27'.
greeter: track various properties persistently
There is a fundamental race condition between PamAuthenticator and the
greeter views. PA is a singleton that emits signals that result in
stateful changes to the views (e.g. showing the prompt message).
Meanwhile views are added when they get connected. This leads to
circumstances where pam may have sent a prompt before a view was
created, meaning the view is in an incorrect state.
To mitigate the problem we'll force-emit a number of stateful signals
whenever they are connected to. Thus ensuring that greeter views
definitely receive the most recent states.
The more long-term solution should likely be to move to property
bindings instead, so these stateful signals are now also exposed as
stateful properties.
(cherry picked from commit a9273c87e8582be7aa1e3de14d92b80ec92c4f44)
M +77 -4 greeter/pamauthenticator.cpp
M +21 -0 greeter/pamauthenticator.h
https://invent.kde.org/plasma/kscreenlocker/commit/161f9d4c5151e4f3871e670531883bcb6a198d1f
--
You are receiving this mail because:
You are watching all bug changes.
