https://bugs.kde.org/show_bug.cgi?id=452118
--- Comment #23 from Michael Butash <mich...@butash.net> --- So weirdly a few days ago, my application windows started moving and resizing bonkers for me again, moving into weird places, resizing windows horizontally to as thin as only 5px wide, and like this report, moving some of them almost entirely off the bottom window of the screen (ending up sometimes hidden by my latte dock) when my external monitors are disconnected. It had been working after clearing out my kscreen and plasma config files, but now randomly as of a few days ago again it's getting extreme (and extremely annoying). I've been looking into where this window placement location state data might be kept, but saw nothing in various kwin or kscreen files across .config or .local configs or resources. After my kscreen wipe, window placements were not restoring after screen changes at all, and added back a kwin script restoreToScreen which I have used prior, and worked well at first, but a few days ago suddenly madness ensued, so I disabled restoreToScreen. Now with it disabled for days, some windows stay in the right places, some get moved but remain proper geometry, other windows will get squished to like 5px wide, hiding them in my desktop somewhere to be found. What's worse is every time I do it, randomly more things move, and to different places, including off the screen, so something is oddly Finding the github for restoreToScreen, an issue reported by kwin's Zamundaaa that the windows placement to screen restoration functionality was now included in 5.26, but certainly doesn't seem to work or work as intended with multiple displays now since 5.27, so maybe something haywire with the multi-screen changes? I presume the script and native kwin might have conflicted, but disabling the script, or before even using it after the wipe removing it did not or works unpredictably. If I could find where these states are saved, I'd love to flush them, but I can't find the mole to whack. I did file another bug report separately as well, might be a dupe of this, but unsure if both are entirely related as I've had this issue across a few laptops for years now and would like to see this working properly all the time, as I know it's possible if/when it does. https://bugs.kde.org/show_bug.cgi?id=468184 -- You are receiving this mail because: You are watching all bug changes.