https://bugzilla.suse.com/show_bug.cgi?id=1197639 Bug ID: 1197639 Summary: plasma5: windows rearranged after powering displayport attached monitors off and on Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs@opensuse.org Reporter: mkubecek@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I have two 2560x1440 (27") monitors attached to displayport outputs of Radeon 2100WX GPU. Whenever I power both monitors off and later on again, most windows (usually all of them) are moved into the middle area around the edge between the monitors. Windows which are wide enough seem to be moved so that their left edge is at 1920 pixels from the left edge of the left monitor. I'll attach two screenshots in a moment to show an example. The research I did suggests that this is a long known and long unsolved problem caused in part by the fact that unlike with DVI, a displayport attached monitor behaves like unplugged one when powered off. The plasma5 then tries to adjust its window layout to what it deems to be a change in monitors setup. There is a known workaround: disable the KScreen2 service in Startup/Shutdown section of systemsettings5. Plasma then does not try to adjust its layout to (seemingly) plugged/unplugged monitors. Unfortunately, while this workaround worked perfectly in Leap 15.3, it stopped working when I upgraded to Leap 15.4. No matter if KScreen5 is reported as running or not, windows get rearranged. I even tried to kill the kscreen_backend_launcher process and move its binary to prevent plasma starting it again but windows still get rearranged so it happens somewhere else apparently. I also tried wayland session which seemed to help a bit, most windows preserve their positions, but some are not only moved but also get resized, in particular some konsole windows get resized to the default width of 80 characters (from e.g. 160). There are also some other weird effects so it's not really an acceptable solution/workaround yet. -- You are receiving this mail because: You are on the CC list for the bug.