Bug 451979

Summary: [Wayland] [Multi Monitor] Dragging a window to the top stops at panel on other monitor
Product: [Plasma] kwin Reporter: Matt <mattyhoffman7>
Component: multi-screenAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: minor CC: bednarczyk.pawel, fanzhuyifan, nate
Priority: NOR Keywords: wayland-only
Version First Reported In: 5.24.3   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Demonstration of the maximise glitch

Description Matt 2022-03-28 00:41:48 UTC
Created attachment 147779 [details]
Demonstration of the maximise glitch

SUMMARY
On my setup I have a panel at the top of my first display, and no panel on my other display. Sometimes when I drag windows to the top of the screen to maximise them on my second display, it stops at the point on the screen where the panel is on my other monitor. I have attached a demonstration (ignore the cursor glitches I think that's a multi monitor bug in PipeWire but not related to this report)
Haven't tested this on X11 so it might/might not occur there as well. Have reproduced on Debian sid, Arch and openSUSE Tumbleweed all with AMDGPU drivers.


STEPS TO REPRODUCE
1. Have 2 monitors
2. Start a Wayland session
3. Make a panel at the top of the display
4. Maximise a window on the first display by dragging it to the top
5. Attempt to do the same on the other display

OBSERVED RESULT
Dragging up on the second monitor is stopped where the panel is on the first monitor

EXPECTED RESULT
I should be able to drag the window to the proper top of the screen

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.24.3
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.16.16-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-4770K CPU @ 3.50GHz
Memory: 19.5 GiB of RAM
Graphics Processor: AMD Radeon RX 6900 XT

ADDITIONAL INFORMATION
Only tested on Wayland, so might/might not occur on X.
Comment 1 fanzhuyifan 2024-03-07 17:09:54 UTC

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