There isn't a way to change the pointer speed in Wayland. This is important for people who have hi dpi mice, like say, a Roccat Kone XTD. :) On X11, one might create a .conf file like Section "InputClass" Identifier "Mouse0" MatchIsPointer "yes" Option "AccelProfile" "flat" Option "AccelSpeed" "-0.85" EndSection Note the flat acceleration profile, this isn't about mouse acceleration but the actual pointer speed. This functionality is currently impossible (AFAIK) to replicate in kwin on Wayland. This is especially noteworthy an issue for gamers who frequently purchase high end mice with very hi dpi (they go up to 12k now).
Please try using the mouse settings in systemsettings. It is mapped to libinput acceleration.
(In reply to Martin Flöser from comment #1) > Please try using the mouse settings in systemsettings. It is mapped to > libinput acceleration. Hi Martin, thanks for replying. But you invalidated my bug report before understanding it. I specifically said this was NOT ABOUT MOUSE ACCELERATION. Its a bit insulting when one takes the time to write a one of these up, and have it invalidated without someone bothering to understand the issue. First, there isn't a "mouse settings" in system settings. So I'll assume you mean "Input Devices" since that seems to be where mice are dealt with. In that area I find "Pointer acceleration" -- the very same thing I said I was not looking for, and "Pointer threshold" which is related. If you look at the x11 config file that, which has the functionality I am attempting to replicate, it clearly says "flat" acceleration profile -- ie, none. I made it very clear that I was not talking about mouse acceleration. This is NOT INVALID. In the future please don't be so ready to invalidate these things if you don't want community interaction to be discouraged.
There is currently a rewrite of the mouse/input kcm happening to put it on par with the touchpad KCM in Wayland: https://phabricator.kde.org/D8168 That means: In Wayland session using libinput directly to change mouse speed / acceleration profile. Currently the mouse speed (or is it the acceleration?) on KWin Wayland is controlled via a hack by the same value as for X. There is some difficulty for me to grasp on how Windows, X and libinput each define speed, acceleration and acceleration profile (and threshold on X). So I'm not sure that in the end how libinput will handle it is what you're asking for in this bug report. Maybe you can clear this up? See here for how libinput doc describes the terminology: https://wayland.freedesktop.org/libinput/doc/latest/pointer-acceleration.html Note also that Martin for sure wasn't trying to be insulting to you. He probably just has the same difficulties as myself to understand what's the difference between libinput's acceleration vs. acceleration profile vs. speed. Closing the issue doesn't mean your feedback is dismissed. After we understand (with your help) the problem more properly we can reopen the issue at any time. So please reply, if the rewrite of the input kcm with libinput would already solve your issue or if it is something else. I believe gamers normally want to have something like - in Windows terminology - "0 acceleration" (in libinput/X terminology: a flat profile) and only change the overall mouse cursor - in Windows terminology - "speed" (in libinput terminology: acceleration). So the rewrite might just be what you're asking for here.
I implemented the mapping from the old config to libinput in KWin. Given your bug report I simply assumed you were not aware that the config option in the KCM performs the mapping which you had in your xorg config. That's fine, nobody needs to know every option. But if there is one and we get a bug report for that option missing the bug is marked as invalid. If you want to know: I even checked the source code this morning to verify that the config goes to the correct accel thingy in libinput.