https://bugs.kde.org/show_bug.cgi?id=468184
--- Comment #4 from Michael Butash <mich...@butash.net> --- Agree with Gauthier, there are some deeply rooted problems here common to various scenarios folks seem to see in more exotic display setups (sadly anything +1 or more). Checking back in on this, I'd been working with the dev of restoreToScreen that did make some changes, and seems to be much better behaved now, but per Zamundaaa's posting to restoreToScreen's github issues, supposedly kwin does this now too, so which should we really be relying on and/or fixing? If kde should be managing screens without the restoreToScreen kwin script, it certainly doesn't do so properly, so should that be fixed, or simply not used or at least trusted to work? Since restoreToScreen made changes for current kde, my windows mostly track the screens properly again except a few windows, notably virtualbox and gkrellm still that refuse to move, or if so badly. Occasionally however the problems seem to come when my edid adapters or even the display sorta go braindead during a display geometry change event, and kde/kscreen *learns* a new display array profile until I physically reset power on them (reliable hardware is hard to find). When having issues prior, I had some 40-ish display profiles saved by kscreen after 6 months of a new laptop that upon clearing out, life got much better, but again that grows now. When I get severely bad window resizing, it's usually because my displays landed on something new like missing a display suddenly, or displays otherwise change. All displays are 4k however, and in theory nothing should have to change such as a display suddenly going to 640x480 and back, so not sure why it so grossly resizes my windows to like 5px wide, but still normally tall. On a 4k display, when they all move to my 15" display, I hate my life to find and resize back. It should simply never, like ever, do this in its worst days, or have some sympathy to undo it's screw-up to put things back as they were. It would be nice to have a way to manage these auto-learned display array setups to either accept or summarily reject, but either way not retain indefinitely to confuse kde over time, particularly across major versions such as 5.27 with multi-monitor changes. Otherwise, it would be nice to properly scope how kde/kscreen *should* handle window placements with or without external script help. -- You are receiving this mail because: You are watching all bug changes.
