| Summary: | Struts of panels affect windows on other screens with no panels, causing stickiness when dragging close to a screen edge and incorrect maximize areas | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Jonas Rakebrandt <xarblu> |
| Component: | multi-screen | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | john.wayne.cornell, kde, nate, tamius.han |
| Priority: | NOR | Keywords: | multiscreen, wayland-only |
| Version First Reported In: | 5.26.90 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | kwin patch | ||
|
Description
Jonas Rakebrandt
2023-01-29 14:41:16 UTC
A video showing what was described: https://youtu.be/lFZyV1ud-ro Does it stop happening if you disable the "Floating Panel" behavior? As far as I can tell the panel doesn't affect this issue in any way. It can be floating, non-floating, completely gone - the windows get stuck at the same height. Can't reproduce Also can't reproduce with current git master, in either X11 or Wayland. Just updated to 5.27.0 and the issue still exists. However I think I found some more info:
1) This only happens with multiple monitors.
2) When dragging a window that "got stuck" horizontally along the height where it gets stuck
it perfectly aligns with other top located panels.
This leads me to the conclusion that windows snap to panels of other screens.
Is it possible that the panels "snap regions" somehow extend across screen boundaries?
Another video showing this: https://youtu.be/9uAjvfUVa44 Great, I can 100% reproduce that now! Definitely the struts of the panel on a different screen are bleeding into other ones, causing that "stickiness" you're encountering. Created attachment 158812 [details]
kwin patch
Did some digging through kwin's code myself to try finding the issue and the changes in the attached diff are my best bet so far. As far as I can tell this doesn't cause any other issues but fixes this issue. Kind of feels like a hack though.
*** Bug 470496 has been marked as a duplicate of this bug. *** *** Bug 474502 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 349191 *** |