https://bugs.kde.org/show_bug.cgi?id=431419
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
Latest Commit| |https://invent.kde.org/fram
| |eworks/kirigami/commit/b4a6
| |c562cde4e064494e261bc3f6400
| |0cbf628a5
--- Comment #17 from Nate Graham <n...@kde.org> ---
Git commit b4a6c562cde4e064494e261bc3f64000cbf628a5 by Nate Graham, on behalf
of Nicolas Fella.
Committed on 22/01/2021 at 14:51.
Pushed by ngraham into branch 'master'.
Don't manually call reverseTwinsChanged when destructing FormLayout
This line causes a crash when destructing the screenlocker KCM.
It doesn't seem to be caused by reverseTwinsChanged itself but rather by
accessing the Qt object. I don't fully undestand the root cause.
However the call itself appears to be unnecessary since in the line
above we write to reverseTwins and that triggers the changed signal if
needed.
Related: bug 428461
M +0 -1 src/controls/FormLayout.qml
https://invent.kde.org/frameworks/kirigami/commit/b4a6c562cde4e064494e261bc3f64000cbf628a5
--
You are receiving this mail because:
You are watching all bug changes.
