https://bugs.kde.org/show_bug.cgi?id=514969
TraceyC <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|[email protected] |[email protected] Component|general |wayland-generic Version First|unspecified |6.4.5 Reported In| | Resolution|--- |WAITINGFORINFO Product|kwayland |kwin Status|REPORTED |NEEDSINFO --- Comment #5 from TraceyC <[email protected]> --- (In reply to David Jarvie from comment #4) > @TraceyC: Could you please explain how you think an application could > produce window corruption like this? I wouldn't have thought that it was > possible, and that it must be the compositor or window manager or some such > thing. That's why I reassigned it to Wayland. I'm not one of the maintainers of Wayland or KWin (which does window compositing0, nor am I an application developer, so I can't tell you how an application can cause window corruption. In the HTML / CSS world I've seen that when libraries change, positioning can be thrown off and the code has to be updated to adapt. I don't know if that's the case here. Tobias already confirmed this is not caused by KWayland, the library, so putting this back in that category isn't going to move this bug forward or get it in front of people who might be able to help. I'll move this to kwin, they can confirm whether this is a compositor bug or not. Robert, please let us know if this happens with any other applications. Thanks. -- You are receiving this mail because: You are watching all bug changes.
