1This script causes screen-bouncing artifacts in Wayland whenever the screen is locked or the logout/reboot dialogue is displayed. It looks like the script is fighting with KDE, where KDE tries to *really* maximize these "windows", the script applies its gaps, KDE restores the maximization, and so on.
This breaks kscreenlocker (which usually borks the session, though notably not always...ugh).
The involvement of kscreenlocker sent me in the wrong direction for hours, since that component has a troubled (recent) history. The logs aren't very useful if you don't already know that this script was the culprit: thousands of "kwin_core: Adjusted client area would exclude a complete screen, ignore" messages.
I also have the same problem in Wayland, but found a workaround by only setting the "Gap size in the bottom edge" other edges to 0px ! I am using the floating panel at bottom and works perfectly for the maximized windows.
I created a pull request on github that fixed this issue. Hopefully the creator will merge it soon. If you want to compile it yourself, here's the link: https://github.com/ghostcrafter551/maximized-window-gap
Ratings & Comments
10 Comments
1 Forgot to add my review to the last comment. But yes broken atm.
Afraid this one doesn't play nice with KDE Neon 5.26.5. Caused a lot of visual errors and shaking of the maximized window.
It works. But, tiling the window to the left/right make the window disappears until I maximize the window.
1 This script causes screen-bouncing artifacts in Wayland whenever the screen is locked or the logout/reboot dialogue is displayed. It looks like the script is fighting with KDE, where KDE tries to *really* maximize these "windows", the script applies its gaps, KDE restores the maximization, and so on. This breaks kscreenlocker (which usually borks the session, though notably not always...ugh). The involvement of kscreenlocker sent me in the wrong direction for hours, since that component has a troubled (recent) history. The logs aren't very useful if you don't already know that this script was the culprit: thousands of "kwin_core: Adjusted client area would exclude a complete screen, ignore" messages.
I also have the same problem in Wayland, but found a workaround by only setting the "Gap size in the bottom edge" other edges to 0px ! I am using the floating panel at bottom and works perfectly for the maximized windows.
Cannot configure gap sizes :(
I created a pull request on github that fixed this issue. Hopefully the creator will merge it soon. If you want to compile it yourself, here's the link: https://github.com/ghostcrafter551/maximized-window-gap
bro, link is 404.
Correct, it got merged so I deleted my fork. Should have written something, im sorry. But doesn't it work again?
Yeah, there's no configuration/gear button available. tho, I was able to manually change the gap size on the source code.