Summary: | Hang everytime at KDE Partition Manager startup after setting Active Backend to KDE Partition Manager Dummy Backend | ||
---|---|---|---|
Product: | [Applications] partitionmanager | Reporter: | Neil Justice <njjustice> |
Component: | general | Assignee: | Andrius Štikonas <andrius> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | jacky_009, matejm98mthw |
Priority: | NOR | Keywords: | drkonqi |
Version: | 4.2.0 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/system/kpmcore/commit/7f41b7c2aac54c68788ed31d4ebcb7cd509d6c83 | Version Fixed In: | 21.12.2 |
Sentry Crash Report: | |||
Bug Depends on: | |||
Bug Blocks: | 439988 | ||
Attachments: |
KDE Partition Manager blank windows before crash after having previously set Dummy Backend
KDE Partition Manager Dr. Konqi crash dialog after clicking the X while KDE Partition Manager is hanging at startup |
Description
Neil Justice
2021-02-09 20:26:11 UTC
Created attachment 135540 [details]
KDE Partition Manager blank windows before crash after having previously set Dummy Backend
Created attachment 135541 [details]
KDE Partition Manager Dr. Konqi crash dialog after clicking the X while KDE Partition Manager is hanging at startup
Indeed, I can reproduce. Thanks for reporting. *** Bug 447037 has been marked as a duplicate of this bug. *** Git commit 72b4142bcb48ef35f1533e5e5fa491cf15414952 by Andrius Štikonas. Committed on 16/01/2022 at 14:22. Pushed by stikonas into branch 'master'. Fix infinite recursion in dummy backend. M +1 -1 src/plugins/dummy/dummybackend.cpp https://invent.kde.org/system/kpmcore/commit/72b4142bcb48ef35f1533e5e5fa491cf15414952 Git commit 7f41b7c2aac54c68788ed31d4ebcb7cd509d6c83 by Andrius Štikonas. Committed on 16/01/2022 at 14:29. Pushed by stikonas into branch 'release/21.12'. Fix infinite recursion in dummy backend. M +1 -1 src/plugins/dummy/dummybackend.cpp https://invent.kde.org/system/kpmcore/commit/7f41b7c2aac54c68788ed31d4ebcb7cd509d6c83 *** Bug 439988 has been marked as a duplicate of this bug. *** |