https://bugs.kde.org/show_bug.cgi?id=499609
Evert Vorster <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Resolution|UPSTREAM |--- Status|RESOLVED |REOPENED --- Comment #2 from Evert Vorster <[email protected]> --- Don't just close a ticket without confirming, please. I read the linked bug report, and calling it identical is wrong. Some differences: 1. The ticket describes the cursor being laggy on one screen basically all the time. In my case the cursor speed is fine for a random amount of time. Could be minutes, could be hours. THEN it slows down. 2. The ticket describes multiple monitors, on my system it is a single monitor. 3. My issue shows up only when I have the magic trifecta of a non-native resolution, Wayland with custom ICC profile and no kernel parameters, the linked issue has it all the time. I did quite a bit of searching through Google on this issue before I picked kwin as an entry point. I could not find anything remotely like this on the web. The reason I picked kwin as an entry point is that it uses Wayland and draws a software cursor. What I would like from the fine folks here is some pointers on what to check when this bug shows up. Does kwin have a debug mode? I'll go ahead and open a ticket with the amdgpu guys as well, and attack this issue from both ends. -- You are receiving this mail because: You are watching all bug changes.
