https://bugs.kde.org/show_bug.cgi?id=514088
cwo <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Latest Commit| |https://invent.kde.org/plas | |ma/plasma-workspace/-/commi | |t/c6fd8d8b91a2b98f7edede482 | |7daa772e7831287 Status|ASSIGNED |RESOLVED Resolution|--- |FIXED Version| |6.5.5 Fixed/Implemented| | In| | --- Comment #3 from cwo <[email protected]> --- Git commit c6fd8d8b91a2b98f7edede4827daa772e7831287 by Christoph Wolk. Committed on 12/01/2026 at 18:45. Pushed by davidedmundson into branch 'master'. kcms/users: reset dialog state on close button press kcm_users has some shared dialog state handling between the C++ backend and qml. Picking a finger is exclusively handled from the qml side, C++ does not interfere with this state (unless there is an error, in which case it will reset the state to list). The only way out of this state in qml is to actually pick a finger. The dialog (reasonably) has a close button, which calls reject() on the dialog (Kirigami default), but nothing actually binds to that so the dialog remains in the pick finger state at least as far as the button row is concerned, which means no Add button even though the displayed contents (handled independently) have returned to the default list state. There's some logic to reset the state, but only while enrolling - but we were still picking the finger, not enrolling yet. Instead, reset the state when reject is emitted. When calling stopEnrolling, the backend will always reset the dialog state, but do further actions only if actually enrolling (which we're not here). FIXED-IN: 6.5.5 M +1 -0 kcms/users/src/ui/FingerprintDialog.qml https://invent.kde.org/plasma/plasma-workspace/-/commit/c6fd8d8b91a2b98f7edede4827daa772e7831287 -- You are receiving this mail because: You are watching all bug changes.
