Bug 468550

Summary: [X11, Libinput] Selecting flat mouse acceleration profile does nothing
Product: [Plasma] kwin Reporter: Tom Seewald <tseewald>
Component: libinputAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate
Priority: NOR    
Version: 5.27.4   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:

Description Tom Seewald 2023-04-16 00:37:19 UTC
SUMMARY
Using the mouse settings menu to select a 'flat' pointer acceleration profile does not properly set the libinput property, and as a result acceleration cannot be disabled.

This problem started occurring after upgrading from Fedora 37 to Fedora 38, and I am using Xorg.
I am able to set a flat acceleration profile using xinput , so this issue appears to be with Plasma.

STEPS TO REPRODUCE
1. Open mouse settings
2. Select flat acceleration profile
3. Apply settings
4. Check the mouse acceleration profile with xinput

OBSERVED RESULT
The acceleration profile is not changed.

xinput list-props 'BenQ ZOWIE BenQ ZOWIE Gaming Mouse' | grep -i profile
       libinput Accel Profiles Available (305):        1, 1, 1
        libinput Accel Profile Enabled (306):   1, 0, 0
        libinput Accel Profile Enabled Default (307):   1, 0, 0

EXPECTED RESULT
I expect that the flat profile is set, which is "0, 1" not "1, 0, 0".
See: https://wiki.archlinux.org/title/Mouse_acceleration#Disabling_mouse_acceleration

xinput list-props 'BenQ ZOWIE BenQ ZOWIE Gaming Mouse' | grep -i profile
        libinput Accel Profiles Available (305):        1, 1, 1
        libinput Accel Profile Enabled (306):   0, 1
        libinput Accel Profile Enabled Default (307):   1, 0, 0

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 38
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 22.12.3
Qt Version: 5.15.9

ADDITIONAL INFORMATION
To set a flat acceleration profile with xinput: input --set-prop 'BenQ ZOWIE BenQ ZOWIE Gaming Mouse' 'libinput Accel Profile Enabled' 0, 1
Comment 1 Nate Graham 2023-04-17 16:46:11 UTC

*** This bug has been marked as a duplicate of bug 468217 ***