In Plasma-5.16.2 MinimizeAll minimizes the windows on all virtual desktops instead of just on the active one. This is not the case in Plasma-5.12.8/-5.13.5 (QT-5.10.1/Frameworks-5.46.0). The expected/desired behaviour is that only the windows on the active desktop are minimized. *** Plasma-5.16.2 Frameworks-5.60.0 QT-5.12.3
OK, the regression pertains to the *plasmoid* MinimizeAll. The kwin script minimizeall works as expected.
The code is meant to disengage minimize all mode when you switch virtual desktops or activities. However, it doesn't work because TasksModel doesn't track virtual desktops or activities on its own. Unfortunately, when I fix that, you switch a virtual desktop, it then unminimizes the windows on the now other virutal desktop and KWin moves focus back to whatever window got focuses on that other desktop as a result of unminimizing and switches desktops back...
(In reply to Kai Uwe Broulik from comment #2) > The code is meant to disengage minimize all mode when you switch virtual > desktops or activities. However, it doesn't work because TasksModel doesn't > track virtual desktops or activities on its own. > I see. So something has changed in QT or FW?. It has worked before after all. > Unfortunately, when I fix that, you switch a virtual desktop, it then > unminimizes the windows on the now other virutal desktop and KWin moves > focus back to whatever window got focuses on that other desktop as a result > of unminimizing and switches desktops back... I really hope you can figure out a solution. Perhaps the script might give you a clue. The script provides a keyboard shortcut. But unfortunately I haven't yet found a way to bind it to a button that could replace the plasmoid in the control panel.
> So something has changed in QT or FW?. It got ported from KWindowSystem to libtaskmanager so it works on Wayland
(In reply to Kai Uwe Broulik from comment #4) > > So something has changed in QT or FW?. > > It got ported from KWindowSystem to libtaskmanager so it works on Wayland So it does work on Wayland? If so and if you can't find a better way and if possible at all, you might provisionally fix this with something like if (wayland) wayland_code; X11_code; Using the kwin script might be an alternative - if that still works on Wayland. BTW: the icon in the controlpanel is too small now.
(In reply to Kai Uwe Broulik from comment #4) > > So something has changed in QT or FW?. > > It got ported from KWindowSystem to libtaskmanager so it works on Wayland If you can't see a way to solve this within a reasonable time-frame, you should imo consider withdrawing the plasmoid. The majority of installations probably still runs under X and this new behaviour is so confusingly different that it does more harm than good to the user. I already switched back to the Plasma-5.12-branch.
I have just noticed the same bug on Wayland. bug 410084 seems related. Operating System: Arch Linux KDE Plasma Version: 5.16.90 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1
(In reply to Patrick Silva from comment #7) > I have just noticed the same bug on Wayland. So it's broken - irrespective of the display server protocol. What's left is kwin's MinimizeAll. Do you know a way to bind this to a button that one could use instead of the plasmoid?
To no surprise the problem still exists in Plasma-5.17.5 and 5.18beta. For me it's a real bummer, so I'll stick with 5.12.9 as long as possible. On a more general note: "Have you written a bug report?" is often used in discussions to counter criticism. In some cases perhaps rightly so. But from the perspective of people who *have* written reports even more frustratin than the bug itself is when a *confirmed* bug is not being properly addressed. This may save developers some hours in the short run but over time inevitably leads to erosion of support and allegiance. So don't expect me to again waste my time on writing reports against stable or beta-versions of Plasma, Frameworks or what have you. Or to ask anybody to do so.
Found a crude but effective workaround: simply copied the 5.12.9-version plus its module to 5.17.5. Works like it should with X, don't know about Wayland. To the devs here: re-install the working version for 5.18.0 until you have a fix for this one. This buggy thing here is an imposition. And mind: those who actually *write* a bug-report are just the tip of the iceberg of users affected (and peeved).