SUMMARY On Wayland, Activities panel (Meta+Q) pushes and/or resizes active (and only active) window to the left, instead of just covering it, as the default (Breeze) Task Switcher. It also happens when switching activities through the Meta+Tab shortcut, as the panel is shown as well. Resizing windows constantly is a problem sometimes because it can re-arrange items inside, e.g. Kmail's columns are resized when window width is reduced briefly. Ideally, Activities panel should work the same as the Task switcher and as in X11, and just cover the window, leaving its geometry unchanged. STEPS TO REPRODUCE 1. On wayland, have a maximized window 2. Meta+Q to show Activities panel on the left edge OBSERVED RESULT Active window geometry is changed to avoid it overlapping with the Activities panel, resizing a maximized window or pushing an unmaximized one to the right EXPECTED RESULT Activities panel should be an overlay over the windows and desktop, as is the default Breeze Task Switcher, and windows geometry shouldn't change because of it. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Nixos unstable-small (shown as 22.05) KDE Plasma Version: 5.23.90 (self-compiled) KDE Frameworks Version: 5.90.0 Qt Version: 5.13.3
This reminds of a regression in plasma-framework which made kickoff resize other windows. Did you build plasma-framework from source code too? what commit are you at?
plasma-framework and the rest of kf is at 5.90, self-compiled as well. Notice this is on NixOS, which is known to require some hacks, patches and wrappers to make apps and libs work with non-FSH systems, so if this bug can't be easily reproducible on other systems, this can be closed as downstream.
Yeah, works fine on my machine (I rebuilt plasma today).
Would you have any hint on what could be causing this issue? Maybe some wrapper failing some .desktop or window class detection on the Activities/plasma panel?
Also cannot reproduce with everything from current git master.
After getting reports that this bug was also an issue in Gentoo, but that it's fixed with kf5 git, I went looking for patches which may have fixed it[1]. It seems that this is not a downstream bug, affects plasma 5.24 with kf5 5.90, but already got fixed by https://invent.kde.org/frameworks/plasma-framework/-/commit/d40d36057a0ee9fcb4badc7ff8b56844da79dfc8 and https://invent.kde.org/frameworks/plasma-framework/-/commit/b882b34d7b55975f679133ef86cfd12869e8bba5 Compiling plasma-framework 5.90 with those patches applied fixes the bug. [1] https://github.com/NixOS/nixpkgs/pull/158716#issuecomment-1034442574