| Summary: | Cursor jumps while moving | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] kwayland | Reporter: | temptempor |
| Component: | general | Assignee: | Martin Flöser <mgraesslin> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | major | CC: | kde, kwin-bugs-null, nate, ready2rumbel, rosswzyang, thesacredsin |
| Priority: | VHI | Keywords: | regression |
| Version: | 5.98.0 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| URL: | https://gitlab.freedesktop.org/mesa/mesa/-/issues/7351 | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=459523 | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: |
Vid1
example2 |
||
Created attachment 152367 [details]
example2
Completely rebooted the system and behavior persists. *** Bug 459566 has been marked as a duplicate of this bug. *** Folks are saying this started happening after they updated their KWayland framework to a version that includes https://invent.kde.org/frameworks/kwayland/-/commit/4c0bba5fd5b33dc90860787372d253f017a4862b and https://invent.kde.org/frameworks/kwayland/-/commit/d02188ad1f6222215adcf842f4c9806ba9e62ccb. *** Bug 459561 has been marked as a duplicate of this bug. *** Comments in the last duplicate are extremely relevant (if true) QQC2 Upgrade causes cursor detection issues in Wayland, issue was not in qqc2-desktop-style-5.97.0-1.fc36.x86_64 Upgraded to qqc2-desktop-style-5.98.0-1.fc36.x86_64 (In reply to David Edmundson from comment #6) > Comments in the last duplicate are extremely relevant (if true) > > QQC2 Upgrade causes cursor detection issues in Wayland, issue was not in > qqc2-desktop-style-5.97.0-1.fc36.x86_64 > Upgraded to qqc2-desktop-style-5.98.0-1.fc36.x86_64 Downgraded to 5.97 in Arch still happening. Worth to note, there was also a Mesa update on that day(In reply to temptempor from comment #7) > (In reply to David Edmundson from comment #6) > > Comments in the last duplicate are extremely relevant (if true) > > > > QQC2 Upgrade causes cursor detection issues in Wayland, issue was not in > > qqc2-desktop-style-5.97.0-1.fc36.x86_64 > > Upgraded to qqc2-desktop-style-5.98.0-1.fc36.x86_64 > > Downgraded to 5.97 in Arch still happening. Worth to note, there was also a Mesa update on that day. What GPU are you running and what Mesa version? (In reply to thesacredsin from comment #8) > Worth to note, there was also a Mesa update on that day(In reply to > temptempor from comment #7) > > (In reply to David Edmundson from comment #6) > > > Comments in the last duplicate are extremely relevant (if true) > > > > > > QQC2 Upgrade causes cursor detection issues in Wayland, issue was not in > > > qqc2-desktop-style-5.97.0-1.fc36.x86_64 > > > Upgraded to qqc2-desktop-style-5.98.0-1.fc36.x86_64 > > > > Downgraded to 5.97 in Arch still happening. > > Worth to note, there was also a Mesa update on that day. What GPU are you > running and what Mesa version? Good notice. The problem happens somewhere between Mesa 22.2.0 - 22.3.x. I was running the Git version. Stable is 22.2.0 Rolled back Mesa to 22.3.0-git.20220921 and issue is now fixed (In reply to thesacredsin from comment #10) > Rolled back Mesa to 22.3.0-git.20220921 and issue is now fixed Did you pinpoint the commit? It should be worth reporting it on Mesa issue tracker. That would be a good idea. See https://docs.mesa3d.org/bugs.html. Once you file a bug report for Mesa, can you add its URL to the URL field of this bug report? Thanks! Disabling mesa glthread globally seems to be the current work-around. What is/are the process/es that Plasma runs that could be added to Mesa's glthread exclusion list (in order to have glthread enabled by default globally but that it doesn't apply to Plasma)? For those interested, the process that Mesa glthread needs excluding for is kwin_wayland. I'm assuming that Mesa will add it in but until then you can resolve this manually by creating a file labelled .drirc, with the following info, and place it in ~/ (home folder):
<device driver="radeonsi">
<application name="kwin_wayland" executable="kwin_wayland">
<option name="mesa_glthread" value="false" />
</application>
</device>
This issue is fixed with Mesa commit 53e7f3af (https://gitlab.freedesktop.org/mesa/mesa/-/commit/53e7f3afbd206a419f01ff77f2ca69697acb23b9) |
Created attachment 152364 [details] Vid1 SUMMARY Mouse cursors starts "jumping" pixels away, focus on items not directly under where the cursor is. Noticed first on Wayland / Intel / Plasma multi-monitor setups for applications on external monitors. Just started happening on main machine. No idea what triggered it, logged out/in because XWayland crashed and there was no way to respawn it and now this problem is happening. Small buttons etc. become impossible to click as they're systematically "jumped from" and you have to blindly guess where the cursor aim translates / where it'll actually click. STEPS TO REPRODUCE 1. No real idea how to reliably re-create this situation. OBSERVED RESULT See attachment. EXPECTED RESULT Usual mouse behaviour SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.9-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 62.7 Gio of RAM Graphics Processor: AMD Radeon RX 6900 XT Manufacturer: Micro-Star International Co., Ltd Product Name: MS-7B86 System Version: 3.0 ADDITIONAL INFORMATION