Bug 1227522

Summary: Mouse acceleration doesn't change
Product: [Fedora] Fedora Reporter: André Martins <aanm90>
Component: plasma-systemsettingsAssignee: Rex Dieter <rdieter>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: bitmage, bob, hdegoede, jan.public, jgrulich, kde-sig, long, me, peter.hutterer, rdieter, than, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-29 12:00:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description André Martins 2015-06-02 21:50:32 UTC
Description of problem:
Mouse acceleration doesn't seem change if I've set a different value under
xset m 1000/100 1
or even in kde mouse settings 

Always


Additional info:

I've a hi-dpi screen (MBP 15" with a 2880x1800 resolution) my mouse is a wireless external from Logitech 705m

Comment 1 Peter Hutterer 2015-06-03 00:52:35 UTC
the default driver in F22 is xorg-x11-drv-libinput which uses libinput underneath. libinput does pointer acceleration itself and disables in-server pointer acceleration so the xset command does nothing.

the KDE settings should know about this though and adjust the right property.

run xinput list-props <device name> before/after changing in KDE - does the "libinput Accel Speed property" change?

Comment 2 André Martins 2015-06-03 09:58:13 UTC
[aanm@localhost ~]$  xinput list                                                                                                                                                                                                 
⎡ Virtual core pointer                          id=2    [master pointer  (3)]                                                                                                                                                                 
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]                                                                                                                                                                 
⎜   ↳ bcm5974                                   id=11   [slave  pointer  (2)]                                                                                                                                                                 
⎜   ↳ Logitech M705                             id=12   [slave  pointer  (2)]                                                                                                                                                                 
⎜   ↳ Logitech K360                             id=13   [slave  pointer  (2)]                                                                                                                                                                 
⎣ Virtual core keyboard                         id=3    [master keyboard (2)]                                                                                                                                                                 
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]                                                                                                                                                                 
    ↳ Power Button                              id=6    [slave  keyboard (3)]                                                                                                                                                                 
    ↳ Video Bus                                 id=7    [slave  keyboard (3)]                                                                                                                                                                 
    ↳ Power Button                              id=8    [slave  keyboard (3)]
    ↳ Sleep Button                              id=9    [slave  keyboard (3)]
    ↳ Apple Inc. Apple Internal Keyboard / Trackpad     id=10   [slave  keyboard (3)]
[aanm@localhost ~]$  xinput list-props 12
Device 'Logitech M705':
        Device Enabled (138):   1
        Coordinate Transformation Matrix (140): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
        libinput Accel Speed (312):     0.000000
        libinput Accel Speed Default (313):     0.000000
        libinput Natural Scrolling Enabled (314):       0
        libinput Natural Scrolling Enabled Default (315):       0
        libinput Send Events Modes Available (258):     1, 0
        libinput Send Events Mode Enabled (259):        0, 0
        libinput Send Events Mode Enabled Default (260):        0, 0
        libinput Left Handed Enabled (316):     0
        libinput Left Handed Enabled Default (317):     0
        libinput Scroll Methods Available (318):        0, 0, 1
        libinput Scroll Method Enabled (319):   0, 0, 0
        libinput Middle Emulation Enabled (320):        0
        libinput Middle Emulation Enabled Default (321):        0
        Device Node (261):      "/dev/input/event9"
        Device Product ID (262):        1133, 4123
[aanm@localhost ~]$  #Changing from 20 to 6.8x on kde settigns
[aanm@localhost ~]$  xinput list-props 12
Device 'Logitech M705':
        Device Enabled (138):   1
        Coordinate Transformation Matrix (140): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
        libinput Accel Speed (312):     0.000000
        libinput Accel Speed Default (313):     0.000000
        libinput Natural Scrolling Enabled (314):       0
        libinput Natural Scrolling Enabled Default (315):       0
        libinput Send Events Modes Available (258):     1, 0
        libinput Send Events Mode Enabled (259):        0, 0
        libinput Send Events Mode Enabled Default (260):        0, 0
        libinput Left Handed Enabled (316):     0
        libinput Left Handed Enabled Default (317):     0
        libinput Scroll Methods Available (318):        0, 0, 1
        libinput Scroll Method Enabled (319):   0, 0, 0
        libinput Middle Emulation Enabled (320):        0
        libinput Middle Emulation Enabled Default (321):        0
        Device Node (261):      "/dev/input/event9"
        Device Product ID (262):        1133, 4123

Comment 3 Bobby 2015-06-06 21:01:52 UTC
I can verify this bug as well.  Acceleration works if changes are made with xinput set-prop but KDE settings have no effect.

Comment 4 Kevin Kofler 2015-07-27 22:51:26 UTC
Is this filed at bugs.kde.org yet? This needs to be fixed in upstream KDE.

Comment 5 André Martins 2015-07-27 22:57:32 UTC
(In reply to Kevin Kofler from comment #4)
> Is this filed at bugs.kde.org yet? This needs to be fixed in upstream KDE.

I've add it now, #350688

Comment 6 Kevin Kofler 2016-07-04 12:14:56 UTC
Still happens on F24 as per the duplicate.

Comment 7 Kevin Kofler 2016-07-04 12:15:10 UTC
*** Bug 1352360 has been marked as a duplicate of this bug. ***

Comment 8 Fedora End Of Life 2017-07-25 18:56:42 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 9 Fedora End Of Life 2018-05-03 08:50:30 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 10 Fedora End Of Life 2018-05-29 12:00:59 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.