https://bugs.kde.org/show_bug.cgi?id=468217
--- Comment #1 from Jake <bugs....@ja-ke.tech> --- With a 125 Hz mouse I also experience the issue, so probably not related to polling. It seems to be caused by the recent addition of a custom accel profile and changed interface, which is now also exposed by xf86-input-libinput. Check on the slave pointer id, for example: ``` >$ xinput list >... >⎜ ↳ Logitech MX Master 3 id=17 [slave pointer (2)] With 1.2.1 it had only 2 values (adaptive, flat): >$ xinput list-props 17 | grep 'Accel Profile Enabled' > libinput Accel Profile Enabled (295): 0, 1 > libinput Accel Profile Enabled Default (296): 1, 0 KDE set it correctly the the second/flat. With 1.3.0 there are 3 values (adaptive, flat, custom): >$ xinput list-props 17 | grep 'Accel Profile Enabled' > libinput Accel Profile Enabled (295): 1, 0, 0 > libinput Accel Profile Enabled Default (296): 1, 0, 0 No matter what is selected in KDE it always stays on the first/adaptive profile. Another workaround is to set it with xinput, then it behaves flat like before: >$ xinput set-prop 17 'libinput Accel Profile Enabled' 0 1 0 -- You are receiving this mail because: You are watching all bug changes.
