https://bugs.documentfoundation.org/show_bug.cgi?id=145220
Michael Weghorn <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED See Also| |https://bugs.kde.org/show_b | |ug.cgi?id=443787 Resolution|--- |NOTOURBUG --- Comment #7 from Michael Weghorn <[email protected]> --- Today, Plasma 5.23 reached Debian testing, and I could reproduce the issue here. Turns out this is not a LibreOffice problem, but a KWin regression, already fixed in the 'Plasma/5.23' branch by this commit: commit 2958881264caf8d3bd83a34411e9586f8fcb7211 Author: Vlad Zahorodnii <[email protected]> Date: Fri Oct 15 17:18:43 2021 +0300 Restore old behavior of Workspace::clientArea(clientOpt, Toplevel) When geometry updates are blocked, the output doesn't get updated. This breaks Workspace::clientArea() overload that takes only the window. Previously, clientArea() would look up the output where the window is every time it's called, so the fact that the screen id or AbstractOutput is unsynchronized with the frame geometry was irrelevant. This change restores the old behavior as 5.23 is affected by the output() being out of sync with the frameGeometry(). Specifically, when kwin starts managing an X11 window, it will block geometry updates, setup the window, e.g. make it fullscreen, and unblock geometry updates. Since Workspace::clientArea(clientArea, Toplevel) uses the output(), X11Client::setFullScreen() will most likely put the X11 window at a wrong output if it's called inside X11Client::manage(). BUG: 443787 (cherry picked from commit 6d5fc9fd3000cf32ecb63a8252a6f50368f3604d) src/workspace.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) see also https://bugs.kde.org/show_bug.cgi?id=443787 which describes a different use case -- You are receiving this mail because: You are the assignee for the bug.
