https://bugs.kde.org/show_bug.cgi?id=407784
--- Comment #19 from Christoph Feck <cf...@kde.org> --- > when they already said three times IT HAPPENS WHEN COMPOSITING IS ENABLED TOO You didn't understand. If the bug happens when compositing is DISABLED, it cannot be a KWin bug. The window manager doesn't decide when and what to draw on the screen if the compositor is disabled. > then relocate it to wherever it's pertinent instead of rudely closing it as > not a thing. Comment #10 says the issue is between the application (and with that also the libraries and toolkits that it uses), and the X server (and with that also the drivers that it uses). With compositing disabled, KWin doesn't even know when and what the application wants to render. It is simply not involved. I cannot know which of those components is responsible. A good test would be to swap between NVIDIA binary drivers and Mesa drivers (both nouveau and swrast) for OpenGL. They have their share of issues, but it could help to understand the issue. -- You are receiving this mail because: You are watching all bug changes.
