Mouse settings missing from Mouse & Touchpad dialog

Bug #1132063 reported by Colin Law on 2013-02-23
624
This bug affects 173 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Medium
Unassigned
unity-control-center (Ubuntu)
High
Unassigned

Bug Description

On up to date Raring alpha, on System Settings > Mouse & Touchpad the Mouse settings are completely missing. The General and Touchpad sections are there but none for mouse. See attached screenshot.

xinput --list shows
~$ xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ MOSART Semi. 2.4G Keyboard Mouse id=11 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad 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)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Power Button id=8 [slave keyboard (3)]
    ↳ Sleep Button id=9 [slave keyboard (3)]
    ↳ MOSART Semi. 2.4G Keyboard Mouse id=10 [slave keyboard (3)]
    ↳ Dell Dell USB Keyboard id=12 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)]

and from lsusb:
Bus 003 Device 002: ID 062a:3286 Creative Labs Nano Receiver [Sandstrom Laser Mouse SMWLL11]

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: gnome-control-center 1:3.6.3-0ubuntu13
ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
Uname: Linux 3.8.0-7-generic i686
ApportVersion: 2.8-0ubuntu4
Architecture: i386
Date: Sat Feb 23 09:40:41 2013
InstallationDate: Installed on 2012-08-01 (205 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120730.1)
MarkForUpload: True
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu6.1
 deja-dup 25.5-0ubuntu1
 gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1
 gnome-control-center-unity 1.2daily13.02.15-0ubuntu1
 indicator-datetime 12.10.3daily13.02.06-0ubuntu1

Related branches

Colin Law (colin-law) wrote :
Felippe Cerreia (felcerreia) wrote :

May i have the same problem. Here is my xinput list and a screenshot
xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Microsoft Microsoft® 2.4GHz Transceiver v6.0 id=9 [slave pointer (2)]
⎜ ↳ Microsoft Microsoft® 2.4GHz Transceiver v6.0 id=10 [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)]
    ↳ Microsoft Microsoft® 2.4GHz Transceiver v6.0 id=8 [slave keyboard (3)]

Colin Law (colin-law) wrote :

Filippe, could you mark this as affects you too please?

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
Felippe Cerreia (felcerreia) wrote :

I think this problem is related to wireless mouse

Jeff (jdorenbush) wrote :

I also have this problem.

xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Logitech USB Receiver id=9 [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)]
    ↳ Logitech USB Receiver id=8 [slave keyboard (3)]

lsusb
Bus 003 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser

Lisa Schmidt (boxnotify) wrote :

I have this problem too.

xinput -list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ RAPOO RAPOO 2.4G Wireless Device id=13 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=15 [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)]
    ↳ Fujitsu FUJ02B1 id=7 [slave keyboard (3)]
    ↳ Fujitsu FUJ02E3 id=8 [slave keyboard (3)]
    ↳ Video Bus id=9 [slave keyboard (3)]
    ↳ Power Button id=10 [slave keyboard (3)]
    ↳ FH13FF-238 id=11 [slave keyboard (3)]
    ↳ RAPOO RAPOO 2.4G Wireless Device id=12 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)]

Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 05c8:030e Cheng Uei Precision Industry Co., Ltd (Foxlink)
Bus 001 Device 004: ID 1690:0741 Askey Computer Corp. [hex]
Bus 002 Device 003: ID 24ae:2000

Marcus Rugger (marcusrugger) wrote :

I'm experiencing the same problem. The problem is apparently not specific to wireless mice.

Ubuntu 13.04 installed on a Dell Optiplex 990 w/Kensington Orbit Trackball with Scroll Ring (corded).

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ No brand Combo Free KVM id=9 [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)]
    ↳ No brand Combo Free KVM id=8 [slave keyboard (3)]

Changed in gnome-control-center (Ubuntu):
status: Confirmed → Fix Committed
Chris (kyfho23) wrote :

Also affected, WIRED mouse.

Xinput:
Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Microsoft Comfort Curve Keyboard 2000 id=9 [slave pointer (2)]
⎜ ↳ Microsoft Microsoft® Comfort Mouse 4500 id=10 [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)]
    ↳ Microsoft Comfort Curve Keyboard 2000 id=8 [slave keyboard (3)]

Note: For me, the options to check the primary button and double click speed do appear.

Anyone have a suggestion for a workaround? The scrolling speed is way, way, way to fast.

And thank you. Please contact me if you want any more info.

Scryer (scryer) wrote :

Same problem on 13.04, wired ASUS R.O.G. mouse.

$ xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ ASUS Laser GAMING MOUSE id=9 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad 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)]
    ↳ Sleep Button id=8 [slave keyboard (3)]
    ↳ USB 2.0 UVC HD Webcam id=10 [slave keyboard (3)]
    ↳ Asus WMI hotkeys id=11 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)]

Hughie Wilmshurst (t-me-w) wrote :

Same problem here with a cheap ebay wireless mouse, which was working absolutely fine until I installed 13.04 fresh (was previously working on 13.04 after upgrading from 12.10).

$ xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ 2.4GWirelessMouse id=10 [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)]
    ↳ 2.4GWirelessMouse id=9 [slave keyboard (3)]
    ↳ USB Keyboard id=11 [slave keyboard (3)]
    ↳ USB Keyboard id=12 [slave keyboard (3)]
    ↳ Eee PC WMI hotkeys id=13 [slave keyboard (3)]

I have the exact same mouse plugged into my laptop, also running 13.04 (upgraded from 12.10) and that is also working absolutely fine, I can adjust the sensitivity without issue.

Hughie Wilmshurst (t-me-w) wrote :

I can't seem to edit my previous comment, so here's a new one - I just noticed that actually, on my laptop, I am also missing the settings - the settings I do have are for the touchpad, not the wireless mouse I'm using. However, the settings were present in 12.10, as I had to adjust them to reduce the sensitivity.

I have just found an app in Ubuntu Software Centre called "Keyboard & Mouse" which does allow the adjustment of the mouse sensitivity and acceleration, and it has worked, so I recommend anyone else with that issue should try that!

Kevin Xue (mailxuewei) wrote :

same problem with Microsoft standard optical mouse, upgraded form 12.10, did not see this issue before upgrade.
xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Microsft Microsoft Wireless Desktop Receiver 3.1A id=9 [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)]
    ↳ Microsft Microsoft Wireless Desktop Receiver 3.1A id=8 [slave keyboard (3)]
    ↳ gspca_zc3xx id=10 [slave keyboard (3)]

IanWilson (wilson-ianj) wrote :

Same problem with logitech mouse. It is far too fast for me. Upgraded to 13.04 from 12.10

 xinput -list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Logitech USB Receiver id=9 [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)]
    ↳ Logitech USB Receiver id=8 [slave keyboard (3)]

Colin Law (colin-law) wrote :

Does anybody know when this is likely to be released? It was committed three months ago. The problem still exists even in Saucy daily.

Sebastien Bacher (seb128) wrote :

@Colin: where was it commited? it seems like a random user changed wrongly the bug status?

Changed in gnome-control-center (Ubuntu):
status: Fix Committed → New
Colin Law (colin-law) wrote :

@Sebastien, I just assumed that since it was marked committed that it was.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
supersasho (supersasho) wrote :

It's 4 months after release and this trivial thing as changing sensitivy is still not fixed. :(

$ xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ MOSART Semi. 2.4G Keyboard Mouse id=9 [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)]
    ↳ MOSART Semi. 2.4G Keyboard Mouse id=8 [slave keyboard (3)]
    ↳ PWC snapshot button id=10 [slave keyboard (3)]

@supersasho: Since it's (allegedly) trivial, how about you propose a patch to fix it? Or find someone else to help you create such a patch? It's open source.

Whinging that unfixed bugs are trivial isn't a great way to get developers on your side. It just adds to the length of the activity log, and risks a motivated developer glancing at the log and going away muttering 'TL;DR'. :(

Jean-Philippe Orsini (jfi) wrote :

Only "primary button" and "double click" settings are available, missing 'pointer speed', 'drag and drop' and 'double click timeout' settings.

"Microsoft Comfort Mouse 6000" is a wired mouse.

xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Microsoft Comfort Mouse 6000 id=8 [slave pointer (2)]
⎜ ↳ Logitech Logitech Illuminated Keyboard id=10 [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)]
    ↳ Logitech Logitech Illuminated Keyboard id=9 [slave keyboard (3)]

kalman (keri-kalman) wrote :

Same problem. Ubuntu 13.04. No slider for mouse pointer speed.

xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Genius 2.4G Wireless Mouse id=10 [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)]
    ↳ Chicony USB Keyboard id=8 [slave keyboard (3)]
    ↳ Chicony USB Keyboard id=9 [slave keyboard (3)]

Adolfo Jayme (fitojb) on 2013-09-16
Changed in gnome-control-center (Ubuntu):
status: Confirmed → Triaged
importance: Undecided → Medium
Corasol (corasol) wrote :

I was trying out the Ubuntu 13.10 install media, and while I haven't actually installed it, this bug was present on the live system, so I'm assuming it also affects 13.10. Logitech wireless mouse + Thinkpad touchpad/trackpoint.

Jonathan (jonathan-ghostlords) wrote :

Also affects me in Ubuntu 13.10 with a wired USB mouse.

$ xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Microsoft Microsoft® Comfort Mouse 4500 id=8 [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)]
    ↳ NOVATEK USB NETVISTA FULL WIDTH KEYBOARD id=9 [slave keyboard (3)]
    ↳ NOVATEK USB NETVISTA FULL WIDTH KEYBOARD id=10 [slave keyboard (3)]
    ↳ BisonCam, NB Pro id=11 [slave keyboard (3)]

liam (liam-h-riley) wrote :

Same problem with a logitech bluetooth mx1000 using the supplied logitech bluetooth usb adapter.

$ xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Logitech Logitech BT Mini-Receiver id=10 [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)]
    ↳ Logitech Logitech USB Keyboard id=8 [slave keyboard (3)]
    ↳ Logitech Logitech BT Mini-Receiver id=9 [slave keyboard (3)]

Claudio Denega (claudio-am) wrote :

Same problem with a wireless Genius on Ubuntu 13.10 but not with a Genius wired

Wireless (mouse settings missing)

$ xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)]
⎜ ↳ Genius 2.4G Wireless Mouse id=15 [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)]
    ↳ Video Bus id=8 [slave keyboard (3)]
    ↳ Power Button id=9 [slave keyboard (3)]
    ↳ Sleep Button id=10 [slave keyboard (3)]
    ↳ Laptop_Integrated_Webcam_HD id=11 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)]
    ↳ Dell WMI hotkeys id=14 [slave keyboard (3)]

Wired (mouse settings ok)

$ xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)]
⎜ ↳ Genius Optical Mouse id=15 [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)]
    ↳ Video Bus id=8 [slave keyboard (3)]
    ↳ Power Button id=9 [slave keyboard (3)]
    ↳ Sleep Button id=10 [slave keyboard (3)]
    ↳ Laptop_Integrated_Webcam_HD id=11 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)]
    ↳ Dell WMI hotkeys id=14 [slave keyboard (3)]

Fadri Furrer (ffurrer) wrote :

Since there are still a lot of affected users, including me on 13.10.

Changed in gnome-control-center (Ubuntu):
status: Triaged → Confirmed
Florian W. (florian-will) wrote :

This is really annoying because it makes Ubuntu unusable when using some of the DPI selections of my new mouse. The mouse speed setting won't come up with my old mouse, too.

I've added some debug printf() to gnome-control-center "gsd-input-helper.c" in device_type_is_present:
                printf("Result %d: name %s type %d\n", i, device_info[i].name, device_info[i].type);
                printf("Result %d: type %s\n", i, XGetAtomName(GDK_DISPLAY_XDISPLAY (gdk_display_get_default ()), device_info[i].type));

(second line is a memory leak)

And in device_info_is_mouse, where "atom" is the result of the XInternAtom call in that function:
        printf("Mouse atom: %s -> %d\n", XGetAtomName(GDK_DISPLAY_XDISPLAY (gdk_display_get_default ()), atom), atom);

This is the output when opening the mouse panel:
Result 0: name Virtual core pointer type 0
Result 0: type (null)
Mouse atom: MOUSE -> 89
Result 1: name Virtual core keyboard type 0
Result 1: type (null)
Mouse atom: MOUSE -> 89
Result 2: name Virtual core XTEST pointer type 0
Result 2: type (null)
Mouse atom: MOUSE -> 89
Result 3: name Virtual core XTEST keyboard type 0
Result 3: type (null)
Mouse atom: MOUSE -> 89
Result 4: name Power Button type 88
Result 4: type KEYBOARD
Mouse atom: MOUSE -> 89
Result 5: name Power Button type 88
Result 5: type KEYBOARD
Mouse atom: MOUSE -> 89
Result 6: name AT Translated Set 2 keyboard type 88
Result 6: type KEYBOARD
Mouse atom: MOUSE -> 89
Result 7: name Holtek USB Gaming Mouse type 88
Result 7: type KEYBOARD
Mouse atom: MOUSE -> 89
Result 8: name Holtek USB Gaming Mouse type 88
Result 8: type KEYBOARD
Mouse atom: MOUSE -> 89
Result 9: name USB Multi-Smart Mouse type 88
Result 9: type KEYBOARD
Mouse atom: MOUSE -> 89

Clearly, all of the mouse entries (old mouse is the Multi-Smart one, new mouse is the Holtek one) use the KEYBOARD type aka atom 88, while no device uses the MOUSE atom number 89. So gnome-control-center assumes there are no mice because mouse_is_present() returns false.

At the same time, xinput --list shows this (so one of the KEYBOARD entries for my Holtek mouse was correct, while the second entry should be MOUSE and the Multi-Smart mouse should have a MOUSE entry only):
$ xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Holtek USB Gaming Mouse id=9 [slave pointer (2)]
⎜ ↳ USB Multi-Smart Mouse id=11 [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)]
    ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)]
    ↳ Holtek USB Gaming Mouse id=8 [slave keyboard (3)]

So XListInputDevices appears to return the wrong device type? I'm afraid of X server internals, so I guess this is a dead end for me.

Florian W. (florian-will) wrote :

Another note, the xinput utility uses the "XIQueryDevice" (apparently part of xinput2) function instead of "XListInputDevices" (xinput1?) if xinput2 is available. gnome-control-center always uses XListInputDevices. That probably explains the difference between xinput --list and the debug output above. It does not explain why results between xinput1 and xinput2 functions differ.

Florian W. (florian-will) wrote :

According to Peter Hutterer (Xorg developer), it's impossible to tell if a device is a mouse or not.
http://who-t.blogspot.de/2009/06/xi2-recipes-part-3.html (see comments)

I guess the best fix in that case is to never hide the mouse settings in gnome-control-center.
Or maybe hide only if there is no xinput2 device with "XIValuatorClassInfo" attached to it, i.e. it would be shown if there is a touchpad but no mouse.

Thee (karavlaz) wrote :

Same problem here with wired MS Confort Mouse 6000 on two different PCs running Ubuntu 14.04
This bug is over a year old, is it going to be fixed?

Mischa (sinnerdenied) wrote :

Also here the problem occures, Microsoft Wireless Mouse, Ubuntu 14.04 32bit.

Solved with the "Keyboard & Mouse" application from software center, as mentioned above here.

Colin Law (colin-law) wrote :

@mischa I don't see any reference to the "Keyboard and Mouse" application earlier in the report. I assume this is referring to lxinput which is an lxde tool. Does it also work with Unity?

Adria (acmesquares) wrote :

Same problem, Microsoft Comfort Mouse 3000

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Microsoft Comfort Mouse 3000 id=11 [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)]
    ↳ Logitech USB Multimedia Keyboard id=9 [slave keyboard (3)]
    ↳ Logitech USB Multimedia Keyboard id=10 [slave keyboard (3)]
    ↳ Eee PC WMI hotkeys id=12 [slave keyboard (3)]

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unity-control-center (Ubuntu):
status: New → Confirmed
Iain Lane (laney) on 2014-10-08
Changed in unity-control-center (Ubuntu):
status: Confirmed → In Progress
assignee: nobody → Iain Lane (laney)
Iain Lane (laney) wrote :

If anyone's on Utopic, please try the package in ppa:laney/expeirmental if/when it builds shortly, cheers.

Iain Lane (laney) wrote :

typo, that's ppa:laney/experimental

Changed in unity-control-center (Ubuntu):
importance: Undecided → High

Still there in 14.10

Florian W. (florian-will) wrote :

Lorenzo, have you tried the PPA referenced by Iain Lane (#35)? I'd love to test that, but I'm still on trusty and the debs don't work. Let me try to build the package locally.

Colin Law (colin-law) wrote :

For me (the original reporter) the bug is fixed in 14.10 without need of the ppa. On the Mouse & Touchpad settings I see the mouse pointer speed as I should.

Florian W. (florian-will) wrote :

I've built (on trusty) and installed the unity-control-center package from the PPA, and unity-settings-daemon from utopic, and now I have a mouse pointer speed option in the settings. That setting was missing when I used the original trusty packages.

Now another problem is that the mouse cursor is pretty fast, even when using the slowest setting. My mouse has a hardware DPI change button though, so I can fix that. :-)

Florian W. (florian-will) wrote :

Sorry, the unity-control-center package was not taken from the PPA, but from the bzr branch linked in this bug report. Not sure if these packages use the same code.

Arno (idfafp) wrote :

Hi, this problem is still there in 15.04.

Colin Law (colin-law) wrote :

It is fixed for me on Ubuntu 15.04 (and was on 14.10). In System Settings > Mouse & Touchpad I see Mouse Pointer Speed ok.

razor7 (ghiamar) wrote :

Hi, I still can't see the mouse speed slider in my Ubuntu 15.04, I have a Logiotech MK320 Wireless Combo, and can't set mouse speed because there is no slider at all!

Confirming for 15.04.
I have Logitech MK240 wireless combo and there is no slider. But if I plug in some separate Logitech wireless mouse or even A4Tech wireless mouse then slider will appear.

enedene (enedene) wrote :

I can confirm this is the case with upcoming 15.10 as well. There is no way, other than command line to set up the mouse speed.

tjagoda (tjagoda) wrote :

Just a workaround here - I am also affected by this bug, but the terminal command xset allows you to adjust the mouse speed using the command line. I suggest doing a man xset to learn more about the command, but "xset m 1.3 0" is the magic number for me. The format of the command is xset m <speed> <threshold>. More explanation on what threshold means can be found in the manpages.

Lexa (lexa) wrote :

Still affects me on 14.04. Would love a backport if/when this gets fixed.

I have a Logitech K260 wireless keyboard+mouse combo (only one receiver for both).
Quick workaround without the command line for me was to plug a normal USB mouse that seems to be recognized correctly.

$ xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Logitech USB Receiver id=10 [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)]
    ↳ Logitech USB Receiver id=9 [slave keyboard (3)]

f(fanta) (fanta) wrote :

Same here on Ubuntu 15.10.

> xinput -list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Lenovo Ultraslim Wireless Keyboard & Mouse id=9 [slave pointer (2)]
⎜ ↳ MOSART Semi. 2.4G Keyboard Mouse id=11 [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)]
    ↳ Lenovo Ultraslim Wireless Keyboard & Mouse id=8 [slave keyboard (3)]
    ↳ MOSART Semi. 2.4G Keyboard Mouse id=10 [slave keyboard (3)]
    ↳ Eee PC WMI hotkeys id=12 [slave keyboard (3)]

Doug Morse (dm-dougmorse) wrote :

Same problem on brand new 15.10 installed yesterday. From searching Google, I see that plugging in a wired mouse brings the settings back, and the pointer speed settings affects both mice. So, I've been able to make the needed adjustment, and it persists. However, disconnecting the wired USB mouse makes the settings again disappear (but the adjustment persists). So presently I have to plug in a wired mouse anytime I want to change the pointer speed.

Krister (thekswenson) wrote :

Nice workaround Doug. I confirm that this bug persists in 15.10 when using the logitech k400 external keyboard/trackpad.

Settings I choose by xset are obviously canceled at the next startup

When I open mouse settings and plug in my A4tech X5-60MD wired mouse, pointer speed setting shows. When I plug it off it dissappears. Now, when I plug in my rapoo 5G wireless mouse, it doesn't show. I plug in again A4tech - they show up

fyo (fyo) wrote :

Clean install of 64bit 15.10 with MS Wireless Laser Keyboard and Mouse 6000. No sensitivity setting.

This has been an issue for years and pretty darn annoying.

Bert (bertmvisser) wrote :

Also clean install 15.10 here (64b), using a *wired* mouse. Only options are double click and primary button.

John (sg86sg) wrote :

Clean 15.10 install, wireless mouse, only options are primary button and double click speed.

On Ubuntu 16.04 beta1, this bug appears (again?).
I'm using WIRELESS mouse, Logitech T400.

juliano (juliano-linuxhell) wrote :

ubuntu version 14.xx = bug mouse speed disappears

ubuntu 15.xx = bug mouse speed disappears

ubuntu 16.xx = bug mouse speed disappears

It is a surprise for so long not be fixed :(

Jo Jaeyoung (jaeyoungse) on 2016-03-31
information type: Public → Public Security
information type: Public Security → Public
Simplehuman (simplehuman) wrote :

Added Xenial to tags, because it is still actual.
Removed unsupported Ubuntu versions from tags.

tags: added: amd64 xenial
removed: raring
a.tlimat@gmail.com (a-tlimat) wrote :

Ubuntu 16.04 LTS
WIRED mouse:

xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ USB Keyboard id=11 [slave pointer (2)]
⎜ ↳ Kingston HyperX 7.1 Audio id=12 [slave pointer (2)]
⎜ ↳ NEWMEN Gaming Mouse id=8 [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)]
    ↳ USB Keyboard id=10 [slave keyboard (3)]
    ↳ NEWMEN Gaming Mouse id=9 [slave keyboard (3)]

i can't see mouse speed and many other settings

JasonSome (jasonmili) wrote :

Hey, same problem here with latest Ubuntu Xenial 16.04 LTS. Fully updated system and still the same problem with no mouse pointer speed and acceleration options!!! Are we going to get any fix anywhere soon?

xinput --list

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ MLK USB Multi-Smart Mouse id=8 [slave pointer (2)]
⎜ ↳ USB USB Keyboard id=10 [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)]
    ↳ USB USB Keyboard id=9 [slave keyboard (3)]
    ↳ UVC Camera (046d:0825) id=11 [slave keyboard (3)]

JasonSome (jasonmili) wrote :

And another weird thing: On dconf-editor on org>gnome>settings-daemon>peripherals>mouse there is no motion acceleration or speed options!!!

pelm (pelle-ekh) wrote :

Happens for me too on Ubuntu 16.04 with a wireless Logitech mouse. Hope someone can fix the problem.

pelm (pelle-ekh) wrote :

I installed "lxinput" and this app, what I can see, works. This is a workaround for now. A workaround I use is also setting "xset m default" as a autostart program.

Over 18 months ago (see #35) this was assigned to Iain Lane. Why has activity stalled?

'lxinput' and/or 'xset' may be workarounds, no doubt of interest to those few who visit this report. But what about the other 99% of users who suffer but have no idea how to search Launchpad and find workarounds? The real benefit of a workaround is that it shows that the job is technically possible and now needs integrating into the product that's delivered to the masses.

Being able to adjust mouse sensitivity is especially important for the elderly and others who suffer from difficulties with motor control. I teach retired beginners and this kind of accessibility issue can make the difference between a happy Linux user and a switch to Windows. See bug #1.

My experience of software development is that if a feature doesn't get done within 6 months then it NEVER gets done. I hope I'm wrong.

modolo (modolo) wrote :

Still there in 16.04
Logitech M165 Wireless Mouse

McGsUbuntu (mcgundels) wrote :

I can not make any mouse settings, only the left or right and double-click speed.
What is the reason for that?
Can you please fix it ...

How it should be (Image): https://drive.google.com/open?id=0B7-HS6U3dpQUMWcwR2U3VGVFNnc

How it is (Image): https://drive.google.com/open?id=0B7-HS6U3dpQUWTlwUWhDdTE4ZTg

McGsUbuntu (mcgundels) wrote :

Sorry...
I can not make any mouse settings, only the left or right and double-click speed.
What is the reason for that?
Can you please fix it or tell me the reason why not...

How it should be (Image): https://drive.google.com/open?id=0B7-HS6U3dpQUMWcwR2U3VGVFNnc

How it is (Image): https://drive.google.com/open?id=0B7-HS6U3dpQUWTlwUWhDdTE4ZTg

My Computer:
Fujitsu Esprimo E9900 - Ubuntu 16.04LTS/Windows 10/RemixOS 2.0 - CPU: Intel®Core™i5 650 4x3.20GHz - Grafik: Intel® Ironlake Desktop - RAM: 6GB

My XINPUT-LIST:
$ xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ 2.4G RF Keyboard & Mouse id=11 [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)]
    ↳ ov519 id=9 [slave keyboard (3)]
    ↳ 2.4G RF Keyboard & Mouse id=10 [slave keyboard (3)]

My LSUSB:
$ lsusb
Bus 002 Device 005: ID 04f3:01a4 Elan Microelectronics Corp. Wireless Keyboard
Bus 002 Device 004: ID 054c:0155 Sony Corp.
Bus 002 Device 006: ID 0db0:6970 Micro Star International MS-6970 BToes Bluetooth adapter
Bus 002 Device 003: ID 0409:0059 NEC Corp. HighSpeed Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Thanx :)

Derek Pockrandt (derekpock) wrote :

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Logitech M570 id=10 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad 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)]
    ↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)]
    ↳ BisonCam, NB Pro id=11 [slave keyboard (3)]

Affects me too, Ubuntu 16.04, but this only affected me after a recent kernel update (it worked before, now it's broken). The lxinput program works for setting mouse-settings, but it does not provide any settings for the touchpad.

Kukri Máté (kukri-mate) wrote :

Seriously??!! This bug was reported 3 years age and it's still isn't fixed on Ubuntu 16.04 LTS. That's a shame!

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.

Iain Lane (laney) wrote :

I (obviously) don't have time to work on this. Back then I submitted a patch to the developers to try to improve detection, but they didn't like it. It's not clear there is a way to detect mice reliably, so one approach might be to just always show the settings even we can't detect a mouse. If someone comes up with such a patch we can consider it.

Changed in unity-control-center (Ubuntu):
status: In Progress → Triaged
assignee: Iain Lane (laney) → nobody
Grant Kim (enpinion) wrote :

I can confirm this and this bug still persists in Ubuntu 16.04.1 LTS

Wired mouse is fine but if only wireless mouse is connected on a system, this bug will appear.
I tested with Logitech M210 and M150

xinput --list output:
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Logitech USB Receiver id=10 [slave pointer (2)]
⎜ ↳ Logitech USB Receiver id=12 [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)]
    ↳ Eee PC WMI hotkeys id=14 [slave keyboard (3)]
    ↳ Logitech USB Receiver id=9 [slave keyboard (3)]
    ↳ Logitech USB Receiver id=11 [slave keyboard (3)

After some investigation as described in comment #27 I found that mouse with type XI_KEYBOARD can be identified by XDeviceInfo->use it always IsXExtensionPointer.

That solve problem for all mouse’s which I found

All who have a problem, please try a PPA:
https://launchpad.net/~roman-shipovskij/+archive/ubuntu/ucc+mouse

After upgrade:
close all Unity Control Center window (if opened);
open new Unity Control Center window;
check settings with and without mouse to ensure that all works as expected;
leave comment here;

My PPA contains packages only for Xenial, I can add updates for other releases if needed

The attachment "Fix missing mouse settings" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Grant Kim (enpinion) wrote :

#75
Thank you for the patch.
With your patch, the problem seems fixed.
So I can confirm #75 patch is valid and works.

pelm (pelle-ekh) wrote :

Thanks alot, it seems to work with the patch, Logitech wireless mouse.

Ubuntu 16.04 with a Microsoft Comfort Sculpt bluetooth mouse. I can confirm that the #75 patch does make the pointer speed slider appear in the control center. However, the slider does not seem to actually affect the mouse speed for me. Bummer.

Magnus Pedersen (so-many-bugs) wrote :

Ubuntu Unity 16.04 with a Roccat Kova mouse. The mouse works fine but I cannot see the controls for mouse-speed and it is moving a bit too fast. I can see the controls for the touch-pad, though. I have not tried the fix mentioned in the last few posts above, because my experience with installing those kinds of things is that it breaks the Linux installation and then I have to reinstall everything. The Ubuntu developers really need to fix this. It is embarrassing that such an important bug has existed for several years.

Sarmad Abdullah (sarmadka-f) wrote :

This affects me as well on 16.04. The mouse settings does not show up for bluetooth mouse, but it does show up when a USB mouse is attached and changes there affect both the USB and the bluetooth mouse. So my workaround is to attach a USB mouse, update the settings, then unplug the USB mouse.

Benedikt Bär (beniwtv) wrote :

Patch in #75 does work for me as well.
Microsoft Wireless Mouse 2000

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Microsoft Microsoft® 2.4GHz Transceiver v7.0 id=11 [slave pointer (2)]
⎜ ↳ Microsoft Microsoft® 2.4GHz Transceiver v7.0 id=12 [slave pointer (2)]
⎜ ↳ audio-technica AT2020USB+ 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)]
    ↳ Power Button id=7 [slave keyboard (3)]
    ↳ XI100DUSB-HDMI id=9 [slave keyboard (3)]
    ↳ Microsoft Microsoft® 2.4GHz Transceiver v7.0 id=10 [slave keyboard (3)]

John Russell (jrussell-88) wrote :

On Yakkety 16.10 x64 this problem still persists

Joseph Borg (joeborg) wrote :

Thanks Roman, that patch works.

Iain Lane (laney) wrote :

Can you ask someone upstream whether the approach is valid?

I think it might be easiest to just always show the settings - what do you think?

Øyvind Stegard (oyvinst) wrote :

Missing sensitivity adjustment for wired USB mouse "1bcf:0824 Sunplus Innovation Technology Inc.", Ubuntu 16.04 with latest HWE.

modolo (modolo) wrote :

Hi!

Bus 003 Device 003: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth

Arch manjaro GNOME

Linux arcturo 4.9.50-1-MANJARO #1 SMP PREEMPT Thu Sep 14 09:07:15 UTC 2017 x86_64 GNU/Linux

The same problem!

computer_freak_8 (j8t8b) wrote :

This still is a problem, even on Ubuntu 17.10 under some (unknown) conditions. Mine used to work with my current mouse, but I went to adjust it today, and it's not there. I have no touchpad, only a mouse; it's a desktop machine.

Sometimes I can plug in a mouse that will make the slider show, but there doesn't seem to be any correlation between what mouse makes it show up... even if it's the same dang thing:

lsusb | grep -i logitech
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
(no speed control)

lsusb | grep -i logitech
Bus 002 Device 012: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
(speed control available)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers