Summary: | Screen locker KCM crashes on destruction in ScreenLockerKcm::~ScreenLockerKcm() after clicking on Appearance button and switching to another KCM | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | NotSchizophrenic28 <gt.ajustis.i> |
Component: | kcm_screenlocker | Assignee: | David Redondo <kde> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | a.nicastro.pub+kde, dan, elf_che, erictsau, fa09d8sf94rdaf, Jarlrusseln, jimtahu, kitt997, leajcastro, med.medin.2014, nanabaahgyan, nate, nemanjamucalovic, norbert, qianshangyin631, rikmills, sarah.azurin, shafff, shmabler |
Priority: | VHI | Keywords: | drkonqi, regression |
Version: | 5.20.5 | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
See Also: |
https://bugs.kde.org/show_bug.cgi?id=428461 https://bugs.kde.org/show_bug.cgi?id=427444 |
||
Latest Commit: | https://invent.kde.org/frameworks/kirigami/commit/b4a6c562cde4e064494e261bc3f64000cbf628a5 | Version Fixed In: | 5.79 |
Sentry Crash Report: |
Description
NotSchizophrenic28
2021-01-11 04:23:28 UTC
*** This bug has been marked as a duplicate of bug 426047 *** Re-opening; I marked this as a duplicate of another bug in error. Can reproduce. Here are the steps: 1. Go to screen locker KCM 2. Click on Appearance button 3. Immediately Switch to any other KCM David, can you have a look? Thanks! *** Bug 431249 has been marked as a duplicate of this bug. *** *** Bug 431472 has been marked as a duplicate of this bug. *** *** Bug 431103 has been marked as a duplicate of this bug. *** *** Bug 431342 has been marked as a duplicate of this bug. *** *** Bug 431040 has been marked as a duplicate of this bug. *** *** Bug 429412 has been marked as a duplicate of this bug. *** *** Bug 431560 has been marked as a duplicate of this bug. *** The related bugs (Bug 428461 and Bug 427444) are about the same thing but have different backtraces. Weird. I did some investigation in https://bugs.kde.org/show_bug.cgi?id=428461#c1 will maybe poke others for help. conceptually closing systemsettings and navigating to another kcm are the same for a kcm, it will be destroyed. A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kirigami/-/merge_requests/210 *** Bug 431572 has been marked as a duplicate of this bug. *** *** Bug 431605 has been marked as a duplicate of this bug. *** *** Bug 431908 has been marked as a duplicate of this bug. *** 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 *** Bug 431599 has been marked as a duplicate of this bug. *** *** Bug 432280 has been marked as a duplicate of this bug. *** *** Bug 432389 has been marked as a duplicate of this bug. *** *** Bug 432454 has been marked as a duplicate of this bug. *** *** Bug 432535 has been marked as a duplicate of this bug. *** *** Bug 433522 has been marked as a duplicate of this bug. *** |