https://bugs.kde.org/show_bug.cgi?id=509669
--- Comment #16 from tempqd <[email protected]> --- Ah I see, so it does seem like specifically KWin's cursor handling then. I also don't have an Intel machine to test atm either. Hmm. > My question is: is it possible to temporarily force KWin to perform these > cursor > updates asynchronously again? How should I go about trying to fix it myself > (ie if it makes sense to somehow bring back connect() for > Cursor::positionChanged > in compositor.cpp)? I'm not sure about these myself currently, but hopefully others might have some thoughts? -- You are receiving this mail because: You are watching all bug changes.
