SUMMARY There are two situations in which I find KScreen is way too eager to change display configuration, which then causes windows to shift in strange ways. Scenario 1) one of several monitors is turned off by accident. It is immediately turned back on, but kscreen has already messed up my screen layouts by trying to re-arrange all my windows onto the two monitors that are still on. This actually happens to me very often because of the where the power button on one of my monitors is. Scenario 2) a power blip causes multiple monitors to turn off simultaneously (assume the monitors are not on the UPS, the main computer is, not an ideal scenario but not uncommon with an underpowered UPS and multiple monitors). In both cases, kscreen very quickly tries to re-arrange windows on the screen, even in the second case where all 3 monitors go off simultaneously, kscreen re-arranges windows in the millisecond timing differences between the monitors turning off. Furthermore, the re-arrangement doesn't even make sense -- I end up with some windows that are halfway across two monitors and other strange things like that. Both scenarios could be handled by making monitor reconfiguration an optional user-driven item -- for example, if kscreen detects a change in screens, it could pop up a dialog box on any screen which is still working with the message: "A screen change configuration was detected, do you want to reconfigure the display?" with an optional count-down to automatically reconfigure within 30 seconds or something like that. Alternately, kscreen could remember the previous window configuration, and if the display configuration returns to the previous setting within a certain time-frame (say 30s), then kscreen could automatically return windows to their previous positions. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 36 KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.3
The real issue here is that when windows are moved automatically because an output becomes unavailable, they aren't moved back when it becomes available again. IIRC that's being worked on.
*** This bug has been marked as a duplicate of bug 455066 ***