https://bugs.kde.org/show_bug.cgi?id=357988
--- Comment #13 from Thomas Lübking <thomas.luebk...@gmail.com> --- - not even restarting the compositor (complete rebuild of GL context) "fixes" it - switching framebuffers (VT2 and back) fixes it Ie. the part of the GL frontbuffer that is related to the particular output is not updated/copied into the scanout buffer until X11 looses and regains the framebuffer. The screen in question is in the middle (so the context isn't too small) and a compositor restart would cause a complete update of the entire scene in a new GL context unconditionally. I'm fairly sure that it's not a bug in KWin, sorry. KWin waits briefly (like 200ms) before moving windows to the remaining workspace, plasmashell (the desktop) might react instantly, so the static framebuffer will be taken at a spot where plasmashell already removed the desktop and kwin has not yet moved the firefox window. If you - suspend the compositor - run glxgears - move it to be partially on the left and partially on the (middle) DP output and - re-attach the DP output: a) glxgears should still cross the screens, otherwise move it into such position b) how much of glxgears updates? -- You are receiving this mail because: You are watching all bug changes.
