https://bugs.kde.org/show_bug.cgi?id=361154
--- Comment #19 from Thomas Lübking <thomas.luebk...@gmail.com> --- What really puzzles me is the nature of this bug. Apparently it's required to start "a game™" which in turn suspends the compositor and then there're artifacts (aka "invalid textures") in 3rd processes and bug #361534 describes "black borders" around even uncomposited windows (falsely mapped shadow windows?) Just suspending the compositor or auto-suspending it along "not games" apparently doesn't cause this. > This bug becomes more annoying when you are using cairo-dock and try to use > opengl applications like Unreal Engine or UInity 3D. > Cairo dock is using opengl and everything gets disable and the only thing you > can see from the dock is a Black Square Dock a) does cairo-dock turn black when simply suspending the compositor? b) does the problem exist when suspending the compositor explicitly and then running the desired game? c) does it exist when applying a kwin rule to not autosuspend compositing for the games? (you can create a blind rule that matches every window to avoid detection of the games) -- You are receiving this mail because: You are watching all bug changes.
