LinuxQuestions.org - Mouse has no sensitivity option after switching to -current from 14.2

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Mouse has no sensitivity option after switching to -current from 14.2 (https://www.linuxquestions.org/questions/slackware-14/mouse-has-no-sensitivity-option-after-switching-to-current-from-14-2-a-4175657756/)

Mouse has no sensitivity option after switching to -current from 14.2

I switched from 14.2 to current and now my mouse has no sensitivity option, only an acceleration option. On 14.2 I could adjust both properties. I installed current from alienbob's iso, and I thought maybe I selected the wrong mouse type during the install, but I also used a different mouse during the install. xinput lists two different mouses and the mouse I actually use has no sensitivity option while the other one does.

Not sure if there's anything I can do to get the sensitivity option back so I can have a 1:1 mouse ratio again, so I'm asking you guys. How can I fix this?

It's a bit old, but maybe this thread can give you some suggestions?
https://www.linuxquestions.org/quest...gs-4175603524/

The problem is that when I do

Code:

xinput list-props

on my mouse there is no property for sensitivity, only acceleration:

Code:

        Device Enabled (149):        1

        Coordinate Transformation Matrix (151):        1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000

        libinput Natural Scrolling Enabled (285):        0

        libinput Natural Scrolling Enabled Default (286):        0

        libinput Scroll Methods Available (287):        0, 0, 1

        libinput Scroll Method Enabled (288):        0, 0, 0

        libinput Scroll Method Enabled Default (289):        0, 0, 0

        libinput Button Scrolling Button (290):        2

        libinput Button Scrolling Button Default (291):        2

        libinput Middle Emulation Enabled (292):        0

        libinput Middle Emulation Enabled Default (293):        0

        libinput Accel Speed (294):        -1.000000

        libinput Accel Speed Default (295):        0.000000

        libinput Accel Profiles Available (296):        1, 1

        libinput Accel Profile Enabled (297):        1, 0

        libinput Accel Profile Enabled Default (298):        1, 0

        libinput Left Handed Enabled (299):        0

        libinput Left Handed Enabled Default (300):        0

        libinput Send Events Modes Available (270):        1, 0

        libinput Send Events Mode Enabled (271):        0, 0

        libinput Send Events Mode Enabled Default (272):        0, 0

        Device Node (273):        "/dev/input/event17"

        Device Product ID (274):        1133, 16465

        libinput Drag Lock Buttons (301):        <no items>

        libinput Horizontal Scroll Enabled (302):        1

Is there anything to do about this? Unfortunately my mouse doesn't have a DPI switch so with 0 acceleration it's super slow.

Also I've been wondering if setting acceleration to 0 actually disables mouse acceleration. I play some FPS games and the mouse just feels off since updating current.

For whatever it's worth I setup a couple of scripts employing various xinput settings along with each game launcher and then adjust the internal game-specific mouse settings to tweak for that game. The internal settings only need to be done once, of course... just like Desktop settings. So I use xinput for baselines and then tweak for the application. works a treat.

Do your scripts adjust the mouse sensitivity property? I don't have that property on -current while on 14.2 I did. I don't know what changed.

Let me just ask, what does the mouse type selection during the ISO installation actually do? Could it be that I selected the wrong mouse type? Does it matter that I used a different mouse during the installation? I don't think any of that should matter, but perhaps?

I suppose it's only a minor inconvenience. My preference is to always keep acceleration off and increase the sensitivity slightly(since I don't have a hardware dpi switch), then in games I can further adjust sensitivity as needed.

In Linux mouse sensitivity is "mouse resolution" but there is apparently some "wiggle room" because different apps use somewhat different labels, with Unity really messing things up by calling "threshold", "resolution". Actual resolution/sensitivity can be adjusted in xorg.conf for global control or via xinput through the somewhat arcane " Coordinate Transformation Matrix" parameter. That is a fairly complex setup so I'm not going to try to explain it here and choose to let you look it up so you can refer to it while you suss it out. It should be noted that one of the reasons that Unity gets away with calling threshold resolution is because they do have a similar feel. You might find you can get a feel you enjoy just by it.

Quote:

Let me just ask, what does the mouse type selection during the ISO installation actually do?

That mouse type is only used for the gpm service (using the mouse when in console), It should not affect the mouse settings in X session.

Slackware 14.2 by default uses evdev as the generic input driver for X instead of libinput that Slackware-current uses. You can try to use evdev as your mouse driver instead of libinput and see if the sensitivity option is back. You can do that by creating a new config file under /etc/X11/xorg.conf.d with the name 99-evdev-mouse.conf with the content:

Code:

Section "InputClass"

        Identifier "evdev pointer catchall"

        MatchIsPointer "on"

        MatchDevicePath "/dev/input/event*"

        Driver "evdev"

EndSection

(You can change the name of the config file to anything that you want actually, just make sure it ends with ".conf" suffix. If there are other .conf files related to libinput inside /etc/X11/xorg.conf.d, make sure the above .conf file is the last file in that directory. Usually by using numbers like "99" above).

Then, restart the X server.

EDIT: Make sure the xf86-input-evdev package is installed.