| Summary: | After a round of 28 updates on May 17, and rebooting, my Plasma Task Manager is broken | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Thomas Andrews <andrewsfarm> |
| Component: | RPM Packages | Assignee: | KDE maintainers <kde> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | release_blocker | CC: | jyri2000, mageia, mhrambo3501 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Thomas Andrews
2017-05-18 04:21:08 CEST
Probably a regression from http://svnweb.mageia.org/packages?view=revision&revision=1102907 and http://svnweb.mageia.org/packages?view=revision&revision=1102908 Assignee:
bugsquad =>
kde
Rémi Verschelde
2017-05-18 07:18:38 CEST
Priority:
Normal =>
release_blocker Definitely, as before these packages updates Task Manager worked OK. Icons only Task Manager shows the same message. CC:
(none) =>
jyri2000 @ Nicolas: Maybe best to revert on the previous state for now, as it's what we have on RC ISOs and is well tested. Once Mageia 6 is released, we could work on a bugfix update via the standard channels, with all the time we need to test it thoroughly. Should be fixed with plasma-workspace-5.8.6-11.mga6, can you confirm? Sorry, no difference. Because I didn't see the problem until after a reboot, I tried rebooting this time, too. Still no change. I guess the package plasma-dessktop should be reverted? At least I got my taskbar back copying /usr/share/plasma/plasmoids/taskbar directory from older plasma-desktop rpm instead of current one... Indeed. Please try plasma-desktop-5.8.6-10.mga6 once it reaches your mirror :) Updating to plasma-desktop-5.8.6-10 on top of plasma-workspace-5.8.6-11 fixed it for me. CC:
(none) =>
mrambo Closing. Resolution:
(none) =>
FIXED Sorry I didn't get back sooner. Bad thunderstorm yesterday afternoon took out my Internet service until 10:00 this morning. Confirming the plasma-desktop-5.8.6-10.mg6 update fixes the problem for me, too. |