Created attachment 129694 [details] Window snapped to left side of screen SUMMARY When using a window with a border of more than 0px width, if you use the auto-snap feature the window will snap to the negative value of the window's border width. If you snap to the top, bottom, or right side, the window does not snap with a negative value. I have observed this on Kubuntu 20.x and KDE Neon 18.x. STEPS TO REPRODUCE 1. Turn on window geometry 2. Set window border to >= 1px 3. Snap window to left side of X-server display 4. Observe negative position. OBSERVED RESULT Window border is snapped out of display bounds only on left side. EXPECTED RESULT Window border does not snap out of display bounds. SOFTWARE/OS VERSIONS Windows: NA macOS: NA Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION Using X-11 display and Nvidia display drivers. Most likely not related to bug.
I have a very similar problem with slight differences. For starter I have a dual screen configuration with a layout like that: T +------+ | | t | +--------+ L| l|r |R | +________+ | | b +------+ B I have assigned a letter to all sides that I could think of. It's ASCII drawing, so, any other "side" would make no sense on my actual setup. L, R : border hidden l, r : border shown T, t : border shown B, b : border hidden Additionally I have a panel on the right side display, at the bottom. That is right above 'b'. Windows will snap on the upper side of the panel, with their border shown. I have not tried other panel positions. My software configuration is: LSB Release: LSB Version: n/a Distributor ID: Gentoo Description: Gentoo Base System release 2.7 Release: 2.7 Codename: n/a Kernel: sys-kernel/gentoo-sources-5.10.27 Display drivers: x11-drivers/nvidia-drivers-460.67 X11 x11-base/xorg-x11-7.4-r3 x11-base/xorg-server-1.20.10-r3 Qt dev-qt/qtcore-5.15.2-r2 KDE kde-plasma/kwin-5.21.3 kde-frameworks/plasma-5.80.0 kde-apps/kio-extras-20.12.3
This bug was reported against an outdated version of KWin. We have made many changes since the. If the issue persists in newer versions can you reopen the bug report updating the version number.