https://bugs.winehq.org/show_bug.cgi?id=57465
--- Comment #10 from Rémi Bernon rbernon@codeweavers.com --- Regarding the KDE issue, I can definitely say it is a KWin bug. I opened https://bugs.kde.org/show_bug.cgi?id=496966 and https://invent.kde.org/plasma/kwin/-/merge_requests/6854 to fix it.
We could perhaps try to work around it but it's IMO brittle. As soon as a window is maximized, any config request will potentially trigger that bug and break KWin state. We could avoid sending config requests to any maximized windows, but these might still be useful to move windows from a monitor to another.
Another option is to temporarily remove the maximized state, send the configure request, and add the maximized state back, but it is getting quite tedious just to workaround a WM bug, and potentially triggering other WM corner cases.