https://bugs.kde.org/show_bug.cgi?id=450301
Kai Krakow <k...@kaishome.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |k...@kaishome.de
--- Comment #12 from Kai Krakow <k...@kaishome.de> ---
I can confirm this. A mostly reliable reproducer is starting a Steam Proton
game which has a launcher that detect DirectX capabilities, e.g. the Elite
Dangerous Launcher. Such launchers generate a full screen window for an blink
of an eye which disables the compositor and automatically enables it again (I'm
forcing composition off through a kwin rule which looks for client windows
named "(gamescope|steam_app_)", otherwise games stutter unpredictably in my
dual monitor setup and both my monitors drift apart with vsync over time (and
X11 always syncs all monitors in a single loop thus syncing to the slowest
monitor).
This tight disable/enable loop seems to be enough to initially trigger the bug
but it usually only occurs when the game ends and closes it's final window
(tho, not exclusively, it still may trigger the bug when the launcher starts).
The game itself is unaffected. Using shift+alt+F12 to disable compositing cures
the flipped and flickering desktop but only until I re-enable compositing. Only
restart kwin_x11 fixes it. After it happened once, it is very likely to be
triggered more easily, a full reboot is needed to get rid of the behavior for a
while.
Games that do not trigger tight enable/disable intervals for compositing seem
to be less likely trigger the bug.
"Force full composition pipeline" is enabled to fix tearing in multimonitor
setups. It may be part of the problem, I was never seeing that on my single
monitor setup (but this is at least 2 years ago).
--
You are receiving this mail because:
You are watching all bug changes.
