Bug 466717

Summary: Tiling window to right half makes it exceed that half
Product: [Plasma] kwin Reporter: Henning <boredsquirrel>
Component: Quick TilingAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: major CC: nate
Priority: NOR Flags: boredsquirrel: Wayland+
boredsquirrel: dpi-
boredsquirrel: Gallium3D-
boredsquirrel: Intel+
boredsquirrel: Mesa+
boredsquirrel: nouveau-
boredsquirrel: NVIDIA-
boredsquirrel: r300g-
boredsquirrel: r600g-
Version: 5.27.1   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:

Description Henning 2023-03-02 13:28:37 UTC
SUMMARY

STEPS TO REPRODUCE
1. Tile a window to the right half using Super+right
2. Tile the window to the left half

OBSERVED RESULT
The windows exceeds the screen limits only on the right half, not on the left

EXPECTED RESULT
Tiling should respect all screen limits

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 37
KDE Plasma Version: 5.27.1
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.14-200.fc37.x86_64 (64-bit)
Graphics Platform: Wayland
Graphics Processor: Mesa IntelĀ® HD Graphics 4000

ADDITIONAL INFO
Screen size set correctly, screen is primary screen. Monitor attached to the left, not affected.

This happens in:
Systemsettings (ssd)
Spotube Flatpak (csd, gtk) (very weird 3-shapes behavior, left, right down, right)
Firewall-configuration (ssd)

doesnt happen:
Flatpak firefox (ssd)
flatpak cryptomator (csd)
flatpak betterbird (ssd)
rpm okular (ssd)
flatpak libreoffice (ssd)
knewstuff dialog (ssd)
signal flatpak (ssd)
flatpak blanket (gtk) (csd)
keepassxc flatpak (ssd)
kwin rules window (ssd)
sudo password request (ssd)
flatpak minder (csd)
pdf arranger flatpak (csd, gtk)
gnome-boxes rpm (gtk, csd)
bottles flatpak (gtk, csd)
db browser flatpak (ssd)
thonny (ssd)
vscodium flatpak (ssd)
kate rpm (ssd)
krita flatpak (ssd)
opensnitch rpm (ssd)
organic maps flatpak (ssd)
freetube flatpak (ssd)
gnu octave flatpak (ssd)
Comment 1 Nate Graham 2023-03-02 21:35:04 UTC

*** This bug has been marked as a duplicate of bug 434615 ***