For me, I'm using a Microsoft Wireless Mobile Mouse 4000, and no
workarounds were working. lxinput and xset both did nothing, however I
did manage to get xinput to work.

I got the id of my mouse from here:

$> xinput --list
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ Microsoft Microsoft® Nano Transceiver v2.0        id=13   [slave  pointer 
 (2)] <- I picked this one
⎜   ↳ Microsoft Microsoft® Nano Transceiver v2.0        id=14   [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)]
    ↳ Power Button                              id=7    [slave  keyboard (3)]
    ↳ Sleep Button                              id=8    [slave  keyboard (3)]
    ↳ HD Webcam C615                            id=9    [slave  keyboard (3)]
    ↳ Apple, Inc Apple Keyboard                 id=10   [slave  keyboard (3)]
    ↳ Apple, Inc Apple Keyboard                 id=11   [slave  keyboard (3)]
    ↳ Microsoft Microsoft® Nano Transceiver v2.0        id=12   [slave  
keyboard (3)]

I picked 13, since there were multiple id's with the same name, and
listed the properties:

$> xinput list-props 13
Device 'Microsoft Microsoft® Nano Transceiver v2.0':
        Device Enabled (152):   1
        Coordinate Transformation Matrix (154): 1.000000, 0.000000, 0.000000, 
0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
        Device Product ID (269):        1118, 1861
        Device Node (270):      "/dev/input/event6"
        Evdev Axis Inversion (285):     0, 0
        Evdev Axes Swap (287):  0
        Axis Labels (288):      "Rel X" (162), "Rel Y" (163), "Rel Horiz Wheel" 
(277), "Rel Dial" (278), "Rel Vert Wheel" (279), "Rel Misc" (280)
        Button Labels (289):    "Button Left" (155), "Button Middle" (156), 
"Button Right" (157), "Button Wheel Up" (158), "Button Wheel Down" (159), 
"Button Horiz Wheel Left" (160), "Button Horiz Wheel Right" (161), "Button 
Side" (275), "Button Extra" (276), "Button Unknown" (273), "Button Unknown" 
(273), "Button Unknown" (273), "Button Unknown" (273)
        Evdev Scrolling Distance (290): 1, 1, 1
        Evdev Middle Button Emulation (291):    0
        Evdev Middle Button Timeout (292):      50
        Evdev Third Button Emulation (293):     0
        Evdev Third Button Emulation Timeout (294):     1000
        Evdev Third Button Emulation Button (295):      3
        Evdev Third Button Emulation Threshold (296):   20
        Evdev Wheel Emulation (297):    0
        Evdev Wheel Emulation Axes (298):       0, 0, 4, 5
        Evdev Wheel Emulation Inertia (299):    10
        Evdev Wheel Emulation Timeout (300):    200
        Evdev Wheel Emulation Button (301):     4
        Evdev Drag Lock Buttons (302):  0

Notice how there is no mention of "Mouse Acceleration" or any such
thing. I suspected that "Coordinate Transformation Matrix" had something
to do with it, so I tried changing the values:

&> xinput --set-prop 13 "Coordinate Transformation Matrix" 1.300000,
0.000000, 0.000000, 0.000000, 1.300000, 0.000000, 0.000000, 0.000000,
1.000000

It worked! I just multiplied the first 2 "1.0000000"'s by the same
number (which I guess are X and Y speed) and now my mouse has a good
speed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132063

Title:
  Mouse settings missing from Mouse & Touchpad dialog

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1132063/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to