https://bugs.kde.org/show_bug.cgi?id=434116
--- Comment #2 from Nate Graham <n...@kde.org> --- Looks like this is a two-part bug: 1. When the window is maximized, we write new position data to the config file even though this doesn't make sense (maximization and position on screen are mutually exclusive concepts). When a window is maximized, we should write to the config file only the fact that the window is maximized and not write out any new position data. 2. When KWin maximizes a window, it remembers the window's prior position internally but only while the window's app is open. If a window is closed while maximized, KWin forgets where the window was last located if that window is re-opened and de-maximized. It needs to be taught how to ask the app to position itself or read the config file itself in this case. -- You are receiving this mail because: You are watching all bug changes.
