https://bugs.kde.org/show_bug.cgi?id=361534
Thomas Lübking <thomas.luebk...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Status|UNCONFIRMED |RESOLVED
--- Comment #8 from Thomas Lübking <thomas.luebk...@gmail.com> ---
I'm not even running KWin (or any KDE or any Qt) anymore...
----
The compositor is suspended because the game asks for that - you can override
that by a rule.
It however hardly explains this behavior nor is overriding it a sane fix to the
problem.
If the artifacts move along the window and are even visible while the
compositor is suspended, the only explanation is an OutputOnly window which is
likely supposed to contain the deco shadows and is for some strange reason not
removed (plus I really thought we'd now have gotten rid of the stupid
window-but-not-the-window shadows)
Also it's not clear whether this is really the cause (see bug #361154, "I can
disable compositing for say the Steam client (in a kwin rule) and launching a
Steam game - does not cause the compositing issues.")
And no: never seen. I've no steam/account, though.
*** This bug has been marked as a duplicate of bug 361154 ***
--
You are receiving this mail because:
You are watching all bug changes.
