GNOME Bugzilla – Bug 701363
Mouse sensitivity not configurable
Last modified: 2021-06-09 16:06:11 UTC
On my Fedora 18 install I am missing the possibility to configure the sensitivity of pointing devices making GNOME hard to use. Please see attached screenshot, showing the empty settings dialog and the Desktop Help suggesting there should be an option to change the pointer speed.
Created attachment 245735 [details] Screenshot, gnome-control-center + Desktop Help
Your mouse is not recognised as a mouse. What's the output of xinput list?
$ xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ ROCCAT ROCCAT Kova 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)] ↳ ROCCAT ROCCAT Kova id=9 [slave keyboard (3)] ↳ Logitech USB Keyboard id=10 [slave keyboard (3)] ↳ Logitech USB Keyboard id=11 [slave keyboard (3)]
Created attachment 245898 [details] lsusb - Maybe it helps
It seems that the: ⎜ ↳ ROCCAT ROCCAT Kova id=8 [slave pointer (2)] device isn't getting recognised as a mouse. Peter, shouldn't pointer devices have at least one of the XI_MOUSE, XI_TRACKBALL, etc. tagged onto it?
Related bug: https://bugs.freedesktop.org/show_bug.cgi?id=62831
Florian: please run evemu-describe against the device and attach the output here. http://www.freedesktop.org/wiki/Evemu/
Created attachment 246002 [details] evemu describe run as root
(In reply to comment #5) > Peter, shouldn't pointer devices have at least one of the XI_MOUSE, > XI_TRACKBALL, etc. tagged onto it? should, but this one looks like a keyboard and a mouse. It has lmr buttons, rel x/y/wheel/dial and keys, so it gets tagged as XI_KEYBOARD. This is generally a bit crap since we cannot know which of the axes is the 'wrong' one. Here too, the Option TypeName seems the sensible solution, like in https://bugs.freedesktop.org/show_bug.cgi?id=55867
I have the same problem with a Logitech MK320 wireless desktop (keyboard + mouse), no mouse speed settings in the GUI. I reported this as a Fedora 19 bug at https://bugzilla.redhat.com/show_bug.cgi?id=1017706, Ondrej Holy suggested I report it here along with the output of xinput list and evemu-describe. $ 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)] ↳ IR-receiver inside an USB DVB receiver id=10 [slave keyboard (3)] ↳ UVC Camera (046d:0990) id=11 [slave keyboard (3)] $ sudo evemu-describe Available devices: /dev/input/event0: Power Button /dev/input/event1: Power Button /dev/input/event2: Logitech USB Receiver /dev/input/event3: Logitech USB Receiver /dev/input/event4: Logitech Logitech Extreme 3D /dev/input/event5: UVC Camera (046d:0990) /dev/input/event6: HDA Intel Front Headphone /dev/input/event7: HDA Intel Line Out Side /dev/input/event8: HDA Intel Line Out CLFE /dev/input/event9: HDA Intel Line Out Surround /dev/input/event10: HDA Intel Line Out Front /dev/input/event11: HDA Intel Line /dev/input/event12: HDA Intel Rear Mic /dev/input/event13: HDA Intel Front Mic /dev/input/event14: HDA NVidia HDMI/DP,pcm=8 /dev/input/event15: HDA NVidia HDMI/DP,pcm=7 /dev/input/event16: HDA NVidia HDMI/DP,pcm=3 /dev/input/event17: IR-receiver inside an USB DVB receiver Select the device event number [0-17]: 3 # EVEMU 1.2 # Input device name: "Logitech USB Receiver" # Input device ID: bus 0x03 vendor 0x46d product 0xc52e version 0x111 # Supported events: # Event type 0 (EV_SYN) # Event code 0 (SYN_REPORT) # Event code 1 (SYN_CONFIG) # Event code 2 (SYN_MT_REPORT) # Event code 3 (SYN_DROPPED) # Event code 4 (FF_STATUS_STOPPED) # Event type 1 (EV_KEY) # Event code 1 (KEY_ESC) # Event code 28 (KEY_ENTER) # Event code 74 (KEY_KPMINUS) # Event code 78 (KEY_KPPLUS) # Event code 103 (KEY_UP) # Event code 105 (KEY_LEFT) # Event code 106 (KEY_RIGHT) # Event code 108 (KEY_DOWN) # Event code 110 (KEY_INSERT) # Event code 111 (KEY_DELETE) # Event code 113 (KEY_MUTE) # Event code 114 (KEY_VOLUMEDOWN) # Event code 115 (KEY_VOLUMEUP) # Event code 116 (KEY_POWER) # Event code 119 (KEY_PAUSE) # Event code 128 (KEY_STOP) # Event code 130 (KEY_PROPS) # Event code 131 (KEY_UNDO) # Event code 133 (KEY_COPY) # Event code 134 (KEY_OPEN) # Event code 135 (KEY_PASTE) # Event code 136 (KEY_FIND) # Event code 137 (KEY_CUT) # Event code 138 (KEY_HELP) # Event code 139 (KEY_MENU) # Event code 140 (KEY_CALC) # Event code 142 (KEY_SLEEP) # Event code 143 (KEY_WAKEUP) # Event code 144 (KEY_FILE) # Event code 150 (KEY_WWW) # Event code 152 (KEY_COFFEE) # Event code 155 (KEY_MAIL) # Event code 156 (KEY_BOOKMARKS) # Event code 158 (KEY_BACK) # Event code 159 (KEY_FORWARD) # Event code 161 (KEY_EJECTCD) # Event code 163 (KEY_NEXTSONG) # Event code 164 (KEY_PLAYPAUSE) # Event code 165 (KEY_PREVIOUSSONG) # Event code 166 (KEY_STOPCD) # Event code 167 (KEY_RECORD) # Event code 168 (KEY_REWIND) # Event code 169 (KEY_PHONE) # Event code 172 (KEY_HOMEPAGE) # Event code 173 (KEY_REFRESH) # Event code 174 (KEY_EXIT) # Event code 176 (KEY_EDIT) # Event code 177 (KEY_SCROLLUP) # Event code 178 (KEY_SCROLLDOWN) # Event code 181 (KEY_NEW) # Event code 182 (KEY_REDO) # Event code 206 (KEY_CLOSE) # Event code 207 (KEY_PLAY) # Event code 208 (KEY_FASTFORWARD) # Event code 209 (KEY_BASSBOOST) # Event code 210 (KEY_PRINT) # Event code 212 (KEY_CAMERA) # Event code 216 (KEY_CHAT) # Event code 217 (KEY_SEARCH) # Event code 219 (KEY_FINANCE) # Event code 223 (KEY_CANCEL) # Event code 226 (KEY_MEDIA) # Event code 228 (KEY_KBDILLUMTOGGLE) # Event code 231 (KEY_SEND) # Event code 232 (KEY_REPLY) # Event code 233 (KEY_FORWARDMAIL) # Event code 234 (KEY_SAVE) # Event code 235 (KEY_DOCUMENTS) # Event code 241 (KEY_VIDEO_NEXT) # Event code 256 (BTN_0) # Event code 272 (BTN_LEFT) # Event code 273 (BTN_RIGHT) # Event code 274 (BTN_MIDDLE) # Event code 275 (BTN_SIDE) # Event code 276 (BTN_EXTRA) # Event code 277 (BTN_FORWARD) # Event code 278 (BTN_BACK) # Event code 279 (BTN_TASK) # Event code 280 ((null)) # Event code 281 ((null)) # Event code 282 ((null)) # Event code 283 ((null)) # Event code 284 ((null)) # Event code 285 ((null)) # Event code 286 ((null)) # Event code 287 ((null)) # Event code 353 (KEY_SELECT) # Event code 354 (KEY_GOTO) # Event code 358 (KEY_INFO) # Event code 362 (KEY_PROGRAM) # Event code 366 (KEY_PVR) # Event code 370 (KEY_SUBTITLE) # Event code 372 (KEY_ZOOM) # Event code 374 (KEY_KEYBOARD) # Event code 376 (KEY_PC) # Event code 377 (KEY_TV) # Event code 378 (KEY_TV2) # Event code 379 (KEY_VCR) # Event code 380 (KEY_VCR2) # Event code 381 (KEY_SAT) # Event code 383 (KEY_CD) # Event code 384 (KEY_TAPE) # Event code 386 (KEY_TUNER) # Event code 387 (KEY_PLAYER) # Event code 389 (KEY_DVD) # Event code 392 (KEY_AUDIO) # Event code 393 (KEY_VIDEO) # Event code 396 (KEY_MEMO) # Event code 397 (KEY_CALENDAR) # Event code 398 (KEY_RED) # Event code 399 (KEY_GREEN) # Event code 400 (KEY_YELLOW) # Event code 401 (KEY_BLUE) # Event code 402 (KEY_CHANNELUP) # Event code 403 (KEY_CHANNELDOWN) # Event code 405 (KEY_LAST) # Event code 408 (KEY_RESTART) # Event code 409 (KEY_SLOW) # Event code 410 (KEY_SHUFFLE) # Event code 416 (KEY_VIDEOPHONE) # Event code 417 (KEY_GAMES) # Event code 418 (KEY_ZOOMIN) # Event code 419 (KEY_ZOOMOUT) # Event code 420 (KEY_ZOOMRESET) # Event code 421 (KEY_WORDPROCESSOR) # Event code 422 (KEY_EDITOR) # Event code 423 (KEY_SPREADSHEET) # Event code 424 (KEY_GRAPHICSEDITOR) # Event code 425 (KEY_PRESENTATION) # Event code 426 (KEY_DATABASE) # Event code 427 (KEY_NEWS) # Event code 428 (KEY_VOICEMAIL) # Event code 429 (KEY_ADDRESSBOOK) # Event code 430 (KEY_MESSENGER) # Event code 432 (KEY_SPELLCHECK) # Event code 433 (KEY_LOGOFF) # Event code 439 (KEY_MEDIA_REPEAT) # Event code 442 (KEY_IMAGES) # Event type 2 (EV_REL) # Event code 0 (REL_X) # Event code 1 (REL_Y) # Event code 6 (REL_HWHEEL) # Event code 7 (REL_DIAL) # Event code 8 (REL_WHEEL) # Event type 3 (EV_ABS) # Event code 32 (ABS_VOLUME) # Value 0 # Min 1 # Max 652 # Fuzz 0 # Flat 0 # Resolution 0 # Event type 4 (EV_MSC) # Event code 4 (MSC_SCAN) # Properties: N: Logitech USB Receiver I: 0003 046d c52e 0111 P: 00 00 00 00 00 00 00 00 B: 00 1f 00 00 00 00 00 00 00 B: 01 02 00 00 10 00 00 00 00 B: 01 00 44 00 00 80 d6 9e 00 B: 01 ed df 41 d9 fa 73 67 00 B: 01 00 c0 17 8b 94 0f 02 00 B: 01 01 00 ff ff 00 00 00 00 B: 01 00 00 00 00 46 44 54 bf B: 01 2d f3 2f 07 ff 7f 83 04 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 02 c3 01 00 00 00 00 00 00 B: 03 00 00 00 00 01 00 00 00 B: 04 10 00 00 00 00 00 00 00 B: 05 00 00 00 00 00 00 00 00 B: 11 00 00 00 00 00 00 00 00 B: 12 00 00 00 00 00 00 00 00 B: 15 00 00 00 00 00 00 00 00 B: 15 00 00 00 00 00 00 00 00 A: 20 1 652 0 0 0
I have the same problem: all I see in the settings panel are "Primary Button" and "Double-click", no sensitivity options... $ 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=14 [slave pointer (2)] ⎜ ↳ Microsoft Microsoft® 2.4GHz Transceiver v6.0 id=16 [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)] ↳ Logitech Logitech Z205 id=9 [slave keyboard (3)] ↳ Integrated Camera id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=11 [slave keyboard (3)] ↳ ThinkPad Extra Buttons id=12 [slave keyboard (3)] ↳ ACPI Virtual Keyboard Device id=13 [slave keyboard (3)] ↳ Microsoft Microsoft® 2.4GHz Transceiver v6.0 id=15 [slave keyboard (3)] $ lsusb Bus 002 Device 004: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth 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 005: ID 17ef:480d Lenovo Integrated Webcam [R5U877] Bus 001 Device 006: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1) Bus 001 Device 004: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor Bus 001 Device 003: ID 046d:0a19 Logitech, Inc. 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
Let us know whether the same problem happens with 3.16, and a newer distribution. The problem should have been fixed by us using libinput-based Xorg driver (or libinput directly in Wayland).
Seeing the same issue on 3.20 (Fedora 23) with a Logitech Deluxe 650 Cordless Desktop (keyboard & mouse combo with cabled USB receiver) - no speed/acceleration options for the mouse. $ 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)] ↳ Power Button id=7 [slave keyboard (3)] ↳ Sleep Button id=8 [slave keyboard (3)] ↳ Logitech USB Receiver id=9 [slave keyboard (3)] ↳ Logitech USB Receiver id=11 [slave keyboard (3)] $ lsusb ... Bus 001 Device 004: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser (I'm guessing the receiver is the same for many sets, or the VID/PID is shared).
what's the output of xinput list-props 10? (the mouse receiver device)
$ xinput list-props 10 Device 'Logitech USB Receiver': Device Enabled (139): 1 Coordinate Transformation Matrix (141): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000 libinput Accel Speed (275): 1.000000 libinput Accel Speed Default (276): 0.000000 libinput Accel Profiles Available (277): 1, 1 libinput Accel Profile Enabled (278): 1, 0 libinput Accel Profile Enabled Default (279): 1, 0 libinput Natural Scrolling Enabled (280): 0 libinput Natural Scrolling Enabled Default (281): 0 libinput Send Events Modes Available (259): 1, 0 libinput Send Events Mode Enabled (260): 0, 0 libinput Send Events Mode Enabled Default (261): 0, 0 libinput Left Handed Enabled (282): 0 libinput Left Handed Enabled Default (283): 0 libinput Scroll Methods Available (284): 0, 0, 1 libinput Scroll Method Enabled (285): 0, 0, 0 libinput Scroll Method Enabled Default (286): 0, 0, 0 libinput Button Scrolling Button (287): 2 libinput Button Scrolling Button Default (288): 274 libinput Middle Emulation Enabled (289): 0 libinput Middle Emulation Enabled Default (290): 0 Device Node (262): "/dev/input/event4" Device Product ID (263): 1133, 50455 libinput Drag Lock Buttons (291): <no items> libinput Horizonal Scroll Enabled (264): 1 Also, for reference: $ xinput list-props 9 Device 'Logitech USB Receiver': Device Enabled (139): 1 Coordinate Transformation Matrix (141): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000 libinput Send Events Modes Available (259): 1, 0 libinput Send Events Mode Enabled (260): 0, 0 libinput Send Events Mode Enabled Default (261): 0, 0 Device Node (262): "/dev/input/event3" Device Product ID (263): 1133, 50455 libinput Horizonal Scroll Enabled (264): 0 $ xinput list-props 11 Device 'Logitech USB Receiver': Device Enabled (139): 1 Coordinate Transformation Matrix (141): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000 libinput Accel Speed (275): 0.000000 libinput Accel Speed Default (276): 0.000000 libinput Accel Profiles Available (277): 1, 1 libinput Accel Profile Enabled (278): 1, 0 libinput Accel Profile Enabled Default (279): 1, 0 libinput Natural Scrolling Enabled (280): 0 libinput Natural Scrolling Enabled Default (281): 0 libinput Send Events Modes Available (259): 1, 0 libinput Send Events Mode Enabled (260): 0, 0 libinput Send Events Mode Enabled Default (261): 0, 0 libinput Left Handed Enabled (282): 0 libinput Left Handed Enabled Default (283): 0 libinput Scroll Methods Available (284): 0, 0, 1 libinput Scroll Method Enabled (285): 0, 0, 0 libinput Scroll Method Enabled Default (286): 0, 0, 0 libinput Button Scrolling Button (287): 2 libinput Button Scrolling Button Default (288): 274 libinput Middle Emulation Enabled (289): 0 libinput Middle Emulation Enabled Default (290): 0 Device Node (262): "/dev/input/event4" Device Product ID (263): 1133, 50455 libinput Horizonal Scroll Enabled (264): 0 Strangely (?) 10 and 11 are *almost* identical: $ diff <(xinput list-props 10) <(xinput list-props 11) 4c4 < libinput Accel Speed (275): 1.000000 --- > libinput Accel Speed (275): 0.000000 25,26c25 < libinput Drag Lock Buttons (291): <no items> < libinput Horizonal Scroll Enabled (264): 1 --- > libinput Horizonal Scroll Enabled (264): 0
this may actually have to do with your specific device. Please file a freedesktop.org bug against xorg component input/libinput, attach an evemu-describe of any device the receiver creates. You can assign the bug to me.
As in model, or a one-off problem with my actual device? I do see pointer acceleration options for other mice (which aren't part of receiver+KB+mouse kits). I've put aside the set now anyway as I was only using it temporarily for a new PC till I got something better; I'll wake this bug up if/when I have it plugged in again and can run evemu-describe etc.
(In reply to Stephen from comment #17) > As in model, or a one-off problem with my actual device? I do see pointer > acceleration options for other mice (which aren't part of receiver+KB+mouse > kits). the libinput xorg driver splits it up into several devices, that's where the issue may stem from.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new bug report at https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/ Thank you for your understanding and your help.