Using KDE 4.9.95 (4.10 RC1), Qt 4.8.4. When moving a maximized window, it is positioned outside the cursors focus. The window should be positioned below the cursor. See the video in the bug URL for a short demonstration. This behaviour might be related to the fact, that I recently had a 2nd display connected to my laptop (X was not restarted since then, only kwin).
We've had such, but it does not occur here (atm) - i'm not sure whether it's related to multiscreen setups. It would indicate that the fakeMove is not processed. Do you have any additional patches or could pot. check whether that call is made (add a qDebug() << "performing fake move";) or inject such debugging patch?
(In reply to comment #1) > It would indicate that the fakeMove is not processed. > Do you have any additional patches or could pot. check whether that call is > made (add a qDebug() << "performing fake move";) or inject such debugging > patch? I don't use any additional patches, plain kwin-4.9.95. Just added a corresponding debug statement to the code and it looks like the fakeMove is not executed. Trying to understand the fakeMove related code now to find out, why it does not happen.
please attach the output of "qdbus org.kde.kwin /KWin supportInformation" fakeMove is only set true in that one location - do you have moveResizeMaximizedWindows enabled (window borders for maximized windows)?
Created attachment 75981 [details] kwin support information Yes, moveResizeMaximizedWindows is enabled in kwinrc. Support information is attached.
random thought: could you try to disable the new Maximize Window effect?
(In reply to comment #4) > Created attachment 75981 [details] > kwin support information > > Yes, moveResizeMaximizedWindows is enabled in kwinrc. Disable it. While the window simply does not resize at all when dragging it out of quick maximization (and rather should not) the two settings are known to conflict. Patch to alter everything and resolve that situation unfortunately will not be in 4.10 (and the publically available version is hardly more than poc)
Ok, disabling "moveResizeMaximizedWindows" solved the initial issue. So I'll just wait for 4.11 and hope the patch to resolve the conflict will be usable by then. Thanks for your investigations. Leaving the bug open until the patch is available in master to be tested.
:-P *** This bug has been marked as a duplicate of bug 295417 ***