| Summary: | new plasma workspace does not allow unlocking of widgets when upgrading from older version | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Parag Shah <pswild13> |
| Component: | RPM Packages | Assignee: | KDE maintainers <kde> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | fri, lewyssmith |
| Version: | 8 | Keywords: | IN_ERRATA8 |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | plasma-workspace-5.20.4-5.mga8.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Parag Shah
2021-02-03 07:43:24 CET
Thank you for the report - and the obscure remedy. Unsure what you mean by 'upgrade'. Are you talking about upgrading from Mageia 7 to 8? Or just applying the most recent M8 update to plasma-workspace? plasma-workspace-5.20.4-5.mga8 I will adjust the title accordingly. In case this cannot be fixed before M8 is released, I am marking this for inclusion in ERRATA. If it *does* get fixed in time, that can be removed. Assigning to KDE team. Assignee:
bugsquad =>
kde After searching on web it appears that the widget lock/unlock bug (or feature removal) is from plasma version 5.18 onwards. Only way to unlock is by the command "qdbus org.kde.plasmashell /PlasmaShell evaluateScript "lockCorona(false)" and to lock: "qdbus org.kde.plasmashell /PlasmaShell evaluateScript "lockCorona(false)" I guess it cant be fixed by Mageia KDE team and it has to go into ERRATA. It will affect all mageia 7 to 8 upgrades. > widget lock/unlock feature removal is from plasma version 5.18 onwards
Thank you for your research & the solution. That should help future sufferers.
Would it be sensible to say in ERRATA:
Plasma5 desktop and panel widgets cannot be locked/unlocked in Plasma version 5.18 onwards. This means that any such widgets locked before the upgrade cannot be unlocked after. So *before* doing a Plasma upgrade, be sure to UNlock all such widgets.
If you do find locked widgets after upgrading, this will unlock them:
$ qdbus org.kde.plasmashell /PlasmaShell evaluateScript "lockCorona(false)"
Entered in Errata, almost verbatim by suggestion, thanks CC:
(none) =>
fri As this bug was for the upgrade path MGA7->MGA8 this should now be no longer applicable for MGA8->MGA9. Is this also valid in MGA9 or why did this land in MGA9 Errata? No longer applicable for MGA9. As MGA8 is going EOL in 3 month and the upgrade path from MGA7-MGA8 is covered by the Errata entry for MGA8, closing this OLD. Status:
NEW =>
RESOLVED |