Bug 474789 - Windows randomly maximized when moved between screens
Summary: Windows randomly maximized when moved between screens
Status: RESOLVED DUPLICATE of bug 349191
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.27.8
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-22 17:11 UTC by gudvinr+kde
Modified: 2023-09-22 20:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Screen layout (19.86 KB, image/png)
2023-09-22 17:11 UTC, gudvinr+kde
Details
Konsole (3.26 MB, image/png)
2023-09-22 17:12 UTC, gudvinr+kde
Details

Note You need to log in before you can comment on or make changes to this bug.
Description gudvinr+kde 2023-09-22 17:11:57 UTC
Created attachment 161807 [details]
Screen layout

SUMMARY

I often have an issue when I drag windows from one screen to another.
Screen layout is in attachment.

When I move window from DELL to BENQ, it might maximize but only by width (i.e. height stays the same and it spans across whole screen by width).

It doesn't happen every time but it happens A LOT.
It doesn't seem to matter if I move window to the middle of the screen or somewhere else.
It is not "expand window on edge" because it expands across all screen, not when I explicitly move window to the edge. And there's no indicator (gray background) of where window will be expanded.


STEPS TO REPRODUCE
1. Move window from screen 2 to screen 1

OBSERVED RESULT
Window expanded across screen width without any indication

EXPECTED RESULT
Window moves saving its screen width unaffected

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.1.54-1-lts (64-bit)
Graphics Platform: X11
Comment 1 gudvinr+kde 2023-09-22 17:12:12 UTC
Created attachment 161808 [details]
Konsole
Comment 2 Nate Graham 2023-09-22 20:38:24 UTC

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