I have two monitor setup (see screenshot of config dialog "dual_screen_config.png"): - primary "Laptop screen" with resolution 1920x1080; - smaller secondary "VGA-1" with resolution 1366x768; - secondary is on left side of primary; - these two monitors forms one big desktop. I can resize window by dragging right edge of window to right till mouse cursor reaches invisible wall somewhere in the middle of desktop (see screenshot "cant_resize.jpg": cursor hits invisible wall). If I want to move window to right by dragging caption bar of window then I also experience mentioned invisible wall: window moves until mouse cursor reaches certain X coordinate (see screenshots "cant_move_1.jpg" and "cant_move_2.jpg": cursor hits invisible wall). This bug I experienced also in v5.5.5. Reproducible: Always
Created attachment 99183 [details] Screenshot of screen config dialog
Created attachment 99184 [details] Resizing: mouse hits invisible wall
Created attachment 99186 [details] Moving: mouse hits invisible wall.
Created attachment 99187 [details] Moving wider window: mouse hits invisible wall.
I think bug #358363 is related to this bug because when taskbar resets its position then during whole session I experience no invisible barrier when mowing or resizing window.
I found another oddity: - I enabled "Taskbar edit" and adjusted height of Taskabar (by using sliders); - I placed Kate's window below Taskbar (screesnshot "kate_window__before.jpeg"); - I increased height of Taskbar by dragging slider down. When bottom border of Taskabar collides with top border of Kate's window then Kate's window "notices in previous posts mentioned invisible barrier" and jumps to left and resizes itself (screenshot "kate_window__after.jpeg").
Created attachment 99982 [details] Adjusting height of Taskabar: before
Created attachment 99983 [details] Adjusting height of Taskabar: after
I think there NVIDIA is involved: when I switch (using NVIDIA X server settings) GPU to Intel then this issue gone.
Thanks for the report Valdas. I'm unable to reproduce this issue on the latest Plasma from git master. Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved, thanks.
I am currently using a different dual screen setup and cannot reproduce the bug.