https://bugs.kde.org/show_bug.cgi?id=489952
--- Comment #21 from Zamundaaa <xaver.h...@gmail.com> --- (In reply to pallaswept from comment #14) > Hmm, I'm not so sure that's the same issue I'm seeing - In this timeframe on > the 120Hz monitor I would have had in the region of hundreds of frames where > it should have drawn the cursor but didn't. If I draw a circle on my desktop > I see several, maybe 10 breaks in that single circle of cursors, and in > these logs I draw many dozens of circles. It's expected that the tool won't capture all dropped cursor updates - it only records data for frames where something except the cursor has changed. So if you move the cursor in a circle and the window below it didn't update, it won't log anything in that duration. That should get fixed with some near-ish future changes in KWin, but for now you could get a more accurate reading by leaving glxgears running on the screens while doing the testing. > Sorry, I forgot about the 'shake cursor' effect. If I draw these test circles > too fast, that kicks in, and that also makes the frame timing smooth. That's an important piece of information... the effect forces a software cursor. If you set the environment variable KWIN_FORCE_SW_CURSOR=1 for KWin, does the issue go away permanently? -- You are receiving this mail because: You are watching all bug changes.
