Hide Forgot
Description of problem: Wireless Logitech mouse connected over Unifying Receiver. Middle button and scrolling are not working. # xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Sony Vaio Jogdial id=8 [slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=12 [slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=13 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS GlidePoint id=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Video Bus id=6 [slave keyboard (3)] ↳ Sony Vaio Keys id=7 [slave keyboard (3)] ↳ Video Bus id=9 [slave keyboard (3)] ↳ Power Button id=10 [slave keyboard (3)] ↳ USB 2.0 Camera id=11 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)] ↳ Sony Vaio Jogdial id=16 [slave keyboard (3)] ↳ Logitech USB Receiver id=17 [slave keyboard (3)] xev does not show any events on pressing middle button. The same is on using scrolling. # libinput-debug-events event6 DEVICE_ADDED Video Bus seat0 default group1 cap:k event8 DEVICE_ADDED Sony Vaio Keys seat0 default group2 cap:k event9 DEVICE_ADDED Sony Vaio Jogdial seat0 default group3 cap:kp scroll-nat event5 DEVICE_ADDED Video Bus seat0 default group1 cap:k event1 DEVICE_ADDED Power Button seat0 default group4 cap:k event13 DEVICE_ADDED USB 2.0 Camera seat0 default group5 cap:k event3 DEVICE_ADDED Logitech USB Receiver seat0 default group6 cap:p left scroll-nat scroll-button event4 DEVICE_ADDED Logitech USB Receiver seat0 default group6 cap:kp scroll-nat event2 DEVICE_ADDED AT Translated Set 2 keyboard seat0 default group7 cap:k event7 DEVICE_ADDED AlpsPS/2 ALPS GlidePoint seat0 default group8 cap:p size 71.43/50.00mm tap(dl off) left scroll-nat scroll-2fg-edge dwt-on event3 POINTER_BUTTON +2.91s BTN_MIDDLE (274) pressed, seat count: 1 Unifying Receiverevent3 POINTER_BUTTON +3.17s BTN_MIDDLE (274) released, seat count: 0 event3 POINTER_BUTTON +9.20s BTN_MIDDLE (274) pressed, seat count: 1 Unifying Receiverevent3 POINTER_BUTTON +9.56s BTN_MIDDLE (274) released, seat count: 0 event2 KEYBOARD_KEY +11.12s KEY_LEFTCTRL (29) pressed event2 KEYBOARD_KEY +11.28s KEY_C (46) pressed So libinput-debug-events shows some events on pressing and releasing middle button but shows nothing on scrolling. # lsusb Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 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 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 005: ID 0489:e00f Foxconn / Hon Hai Foxconn T77H114 BCM2070 [Single-Chip Bluetooth 2.1 + EDR Adapter] Bus 001 Device 004: ID 0c45:64b5 Microdia Bus 001 Device 003: ID 08ff:168f AuthenTec, Inc. AES1660 Fingerprint Sensor Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
run evemu-record against the device please and check if the buttons send any events. If not, there's nothing we can do in userspace because we don't see the events in the first place.
evemu-record Available devices: /dev/input/event0: Lid Switch /dev/input/event1: Power Button /dev/input/event2: AT Translated Set 2 keyboard /dev/input/event3: Logitech USB Receiver /dev/input/event4: Logitech USB Receiver /dev/input/event5: Video Bus /dev/input/event6: Video Bus /dev/input/event7: AlpsPS/2 ALPS GlidePoint /dev/input/event8: Sony Vaio Keys /dev/input/event9: Sony Vaio Jogdial /dev/input/event10: HDA Intel PCH Headphone /dev/input/event11: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event13: USB 2.0 Camera Select the device event number [0-13]: 3 # EVEMU 1.3 # Kernel: 4.8.0-0.rc3.git0.1.fc26.x86_64 # DMI: dmi:bvnINSYDE:bvrR2087H4:bd06/15/2012:svnSonyCorporation:pnVPCSB2M9E:pvrC609C7Z2:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: # Input device name: "Logitech USB Receiver" # Input device ID: bus 0x03 vendor 0x46d product 0xc52f 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 ((null)) # Event code 5 ((null)) # Event code 6 ((null)) # Event code 7 ((null)) # Event code 8 ((null)) # Event code 9 ((null)) # Event code 10 ((null)) # Event code 11 ((null)) # Event code 12 ((null)) # Event code 13 ((null)) # Event code 14 ((null)) # Event type 1 (EV_KEY) # 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 type 2 (EV_REL) # Event code 0 (REL_X) # Event code 1 (REL_Y) # Event code 6 (REL_HWHEEL) # Event code 8 (REL_WHEEL) # Event type 4 (EV_MSC) # Event code 4 (MSC_SCAN) # Properties: N: Logitech USB Receiver I: 0003 046d c52f 0111 P: 00 00 00 00 00 00 00 00 B: 00 0b 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: 01 00 00 ff ff 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: 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 43 01 00 00 00 00 00 00 B: 03 00 00 00 00 00 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: 14 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 ################################ # Waiting for events # ################################ E: 0.000001 0004 0004 589827 # EV_MSC / MSC_SCAN 589827 E: 0.000001 0001 0112 0001 # EV_KEY / BTN_MIDDLE 1 E: 0.000001 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +0ms evemu-recordE: 0.163990 0004 0004 589827 # EV_MSC / MSC_SCAN 589827 E: 0.163990 0001 0112 0000 # EV_KEY / BTN_MIDDLE 0 E: 0.163990 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +163ms E: 2.515985 0004 0004 589827 # EV_MSC / MSC_SCAN 589827 E: 2.515985 0001 0112 0001 # EV_KEY / BTN_MIDDLE 1 E: 2.515985 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +2352ms At least pressing middle button seems is emitting something. However I don't see pasted text on pressing middle button so still seems something is wrong here. Against which one package needs to be raised bug report about scrolling? kernel? If yes .. what I must include in such bug report?
pasting is done by the clients, not in libinput, so this isn't something we can address. check with xev whether you get a button 2 event on middle click and with sudo libinput-debug-events whether you get the event there. If both show it, then it's a client issue. But... evemu-recordE: 0.163990 0004 0004 589827 # EV_MSC / MSC_SCAN 589827 This line in the output suggests that paste is working because I can't think of another reason why that "evemu-record" would be there right after the middle button event :) so you don't see anything from the wheel? did you at any point configure the mouse with the logitech software under windows?
libinput-debug-events shows that middle button emits events. So what could be wrong here that paste from clipboard is not working? and/or what can I check to diagnose this issue? and/or to which one component/package this issue may be related? > so you don't see anything from the wheel? did you at any point configure the mouse with the logitech software under windows? Under Windows this mouse is working without problems and none xev and libinput-debug-events shows any events on scrolling. What I can do more here?
(In reply to Tomasz Kłoczko from comment #4) > libinput-debug-events shows that middle button emits events.\ what does xev show? also, are you on GNOME on Wayland? > Under Windows this mouse is working without problems and none xev and > libinput-debug-events shows any events on scrolling. > What I can do more here? what's the exact model name, do you have a link to the device?
I'm using Logitech M235 Wireless Optical Mouse.
> what does xev show? > also, are you on GNOME on Wayland?
I'm using GNOME. Just checked again and on current kernel (4.8.0-0.rc6.git1.1.fc26.x86_64) xev and libinput-debug-events as well does not show anything on pressing middle button and on trying to scroll.
(In reply to Tomasz Kłoczko from comment #8) > I'm using GNOME. > Just checked again and on current kernel (4.8.0-0.rc6.git1.1.fc26.x86_64) > xev and libinput-debug-events as well does not show anything on pressing > middle button and on trying to scroll. libinput-debug-events doesn't show the middle button/scroll events but evemu does? that's ... unlikely. I'm not even sure what code path you'd be triggering here that this gets filtered (scroll button emulation maybe, but you'd have to enable it on the commandline) so yeah, I'm thoroughly confused now. do you have other kernels to try? what does event4 (the other unifying receiver device) show in evemu-record?
Just finished upgrade to latest kernel and seems now middle button is working. libinput-debug-events -event7 DEVICE_ADDED Video Bus seat0 default group1 cap:k -event9 DEVICE_ADDED Sony Vaio Jogdial seat0 default group2 cap:kp scroll-nat -event8 DEVICE_ADDED Sony Vaio Keys seat0 default group3 cap:k -event6 DEVICE_ADDED Video Bus seat0 default group1 cap:k -event1 DEVICE_ADDED Power Button seat0 default group4 cap:k -event10 DEVICE_ADDED USB 2.0 Camera seat0 default group5 cap:k -event3 DEVICE_ADDED Logitech USB Receiver seat0 default group6 cap:p left scroll-nat scroll-button -event4 DEVICE_ADDED Logitech USB Receiver seat0 default group6 cap:kp scroll-nat -event2 DEVICE_ADDED AT Translated Set 2 keyboard seat0 default group7 cap:k -event5 DEVICE_ADDED AlpsPS/2 ALPS GlidePoint seat0 default group8 cap:p size 71.43/50.00mm tap(dl off) left scroll-nat scroll-2fg-edge dwt-on -event3 POINTER_BUTTON +1.65s BTN_MIDDLE (274) pressed, seat count: 1 libinput-debug-events event3 POINTER_BUTTON +1.75s BTN_MIDDLE (274) released, seat count: 0 event3 POINTER_BUTTON +2.38s BTN_MIDDLE (274) pressed, seat count: 1 libinput-debug-events event3 POINTER_BUTTON +2.43s BTN_MIDDLE (274) released, seat count: 0 event3 POINTER_BUTTON +2.92s BTN_MIDDLE (274) pressed, seat count: 1 libinput-debug-events event3 POINTER_BUTTON +3.19s BTN_MIDDLE (274) released, seat count: 0 event3 POINTER_BUTTON +3.99s BTN_MIDDLE (274) pressed, seat count: 1 c&p is working as well. Feel free to close this ticket :)
Pressing scroll wheel as middle button now is working but scrolling still is not working :( libinput-debug-events does not show any events on scrolling so partially bug still is around :(
middle-button scrolling isn't enabled by default for normal mice, only for trackpoints so you have to enable it manually: xinput set-prop 'device name' 'libinput Scroll Method Enabled' 0 0 1 or add an xorg.conf.d snippet to set it.
I think that someone should reconsider to change this default behavior because this is what you are normally expecting .. I don't remember any windows mouse which driver would even allow disable scrolling. In case all mice scrolling under Windows is always working OOTB.
Just checked status of my mouse efter fresh GUI session: $ xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Sony Vaio Jogdial id=7 [slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=12 [slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=13 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS GlidePoint id=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Video Bus id=6 [slave keyboard (3)] ↳ Sony Vaio Keys id=8 [slave keyboard (3)] ↳ Video Bus id=9 [slave keyboard (3)] ↳ Power Button id=10 [slave keyboard (3)] ↳ USB 2.0 Camera id=11 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)] ↳ Sony Vaio Jogdial id=16 [slave keyboard (3)] ↳ Logitech USB Receiver id=17 [slave keyboard (3)] $ xinput list-props 12 | grep "Scroll Method" libinput Scroll Methods Available (292): 0, 0, 1 libinput Scroll Method Enabled (293): 0, 0, 0 libinput Scroll Method Enabled Default (294): 0, 0, 0 and after change manually as you recommended: $ xinput set-prop 12 'libinput Scroll Method Enabled' 0 0 1 $ xinput list-props 12 | grep "Scroll Method" libinput Scroll Methods Available (292): 0, 0, 1 libinput Scroll Method Enabled (293): 0, 0, 1 libinput Scroll Method Enabled Default (294): 0, 0, 0 And still scrolling is not working and libinput-debug-events does not shows any events on scrolling. Just found ond MS Mouse (USB) and after connecting it scrolling is working OOTB. $ xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Sony Vaio Jogdial id=7 [slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=12 [slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=13 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS GlidePoint id=15 [slave pointer (2)] ⎜ ↳ Microsoft Microsoft Basic Optical Mouse v2.0 id=18 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Video Bus id=6 [slave keyboard (3)] ↳ Sony Vaio Keys id=8 [slave keyboard (3)] ↳ Video Bus id=9 [slave keyboard (3)] ↳ Power Button id=10 [slave keyboard (3)] ↳ USB 2.0 Camera id=11 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)] ↳ Sony Vaio Jogdial id=16 [slave keyboard (3)] ↳ Logitech USB Receiver id=17 [slave keyboard (3)] Scroll settings on this mouse are: $ xinput list-props 18 | grep "Scroll Method" libinput Scroll Methods Available (292): 0, 0, 1 libinput Scroll Method Enabled (293): 0, 0, 0 libinput Scroll Method Enabled Default (294): 0, 0, 0 So these settings are exactly the same as default on Wireless Logitech one.
(In reply to Tomasz Kłoczko from comment #13) > I think that someone should reconsider to change this default behavior > because this is what you are normally expecting .. > I don't remember any windows mouse which driver would even allow disable > scrolling. > In case all mice scrolling under Windows is always working OOTB. fwiw, we look at windows/macos for general guidelines but we don't always copy their settings. in this case iirc button scrolling on windows also has visual feedback which we don't have (and cannot provide in the same way). windows/macos also don't have the reliance on the middle mouse button click events that we have so they have more leeway here. is the right button set for your mouse? what does the libinput Button Scrolling Button property say? (just post the whole xinput list-props output, it's easier to ignore a few lines than guess what's missing) if it works on your MS mouse OOTB without the method being enabled then it's done in firmware, there is not much we can do to stop or aid with that.
> if it works on your MS mouse OOTB without the method being enabled then it's done in firmware, there is not much we can do to stop or aid with that. You mean firmware microcontroller of the mouse sending exact signals to usb port? If it is true I need to know more details about this as I would be able to talk with such details with Logitech support. Another thing is that Logitech mouse is fully working under Windows even without installed logitech software. Middle button emulation by right one is IMO good as in many places right click normally displays some context menu.
(In reply to Tomasz Kłoczko from comment #16) > > if it works on your MS mouse OOTB without the method being enabled then it's done in firmware, there is not much we can do to stop or aid with that. > > You mean firmware microcontroller of the mouse sending exact signals to usb > port? > If it is true I need to know more details about this as I would be able to > talk with such details with Logitech support. > Another thing is that Logitech mouse is fully working under Windows even > without installed logitech software. run evemu-record against the device and look what button events you get. evemu sits below libinput, so whatever it spits out is the data sent from the device. this link should help interpreting the output, but at least for what you're doing it should be fairly intuitive. https://who-t.blogspot.com.au/2016/09/understanding-evdev.html
So .. evemu-record shows nothing. What does it mean? that it is kernel driver issue? If yes: what I can do more to diagnose the issue?
did you run it as root? did you check if the device exposes other event nodes that may send events (some mice have multiple)
Yes I did: [root@domek ~]# evemu-record /dev/input/event3 # EVEMU 1.3 # Kernel: 4.9.0-0.rc5.git4.1.fc26.x86_64 # DMI: dmi:bvnINSYDE:bvrR2087H4:bd06/15/2012:svnSonyCorporation:pnVPCSB2M9E:pvrC609C7Z2:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: # Input device name: "Logitech USB Receiver" # Input device ID: bus 0x03 vendor 0x46d product 0xc52f 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 ((null)) # Event code 5 ((null)) # Event code 6 ((null)) # Event code 7 ((null)) # Event code 8 ((null)) # Event code 9 ((null)) # Event code 10 ((null)) # Event code 11 ((null)) # Event code 12 ((null)) # Event code 13 ((null)) # Event code 14 ((null)) # Event type 1 (EV_KEY) # 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 type 2 (EV_REL) # Event code 0 (REL_X) # Event code 1 (REL_Y) # Event code 6 (REL_HWHEEL) # Event code 8 (REL_WHEEL) # Event type 4 (EV_MSC) # Event code 4 (MSC_SCAN) # Properties: N: Logitech USB Receiver I: 0003 046d c52f 0111 P: 00 00 00 00 00 00 00 00 B: 00 0b 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: 01 00 00 ff ff 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: 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 43 01 00 00 00 00 00 00 B: 03 00 00 00 00 00 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: 14 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 ################################ # Waiting for events # ################################ ^C[root@domek ~]#
what does the other device show? event4 according to comment 0
[root@domek ~]# evemu-record /dev/input/event4 # EVEMU 1.3 # Kernel: 4.9.0-0.rc8.git2.1.fc26.x86_64 # DMI: dmi:bvnINSYDE:bvrR2087H4:bd06/15/2012:svnSonyCorporation:pnVPCSB2M9E:pvrC609C7Z2:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: # Input device name: "Logitech USB Receiver" # Input device ID: bus 0x03 vendor 0x46d product 0xc52f 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 ((null)) # Event code 5 ((null)) # Event code 6 ((null)) # Event code 7 ((null)) # Event code 8 ((null)) # Event code 9 ((null)) # Event code 10 ((null)) # Event code 11 ((null)) # Event code 12 ((null)) # Event code 13 ((null)) # Event code 14 ((null)) # 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 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 171 (KEY_CONFIG) # 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 224 (KEY_BRIGHTNESSDOWN) # Event code 225 (KEY_BRIGHTNESSUP) # 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 240 (KEY_UNKNOWN) # Event code 241 (KEY_VIDEO_NEXT) # Event code 244 (KEY_BRIGHTNESS_AUTO) # Event code 256 (BTN_0) # 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 407 (KEY_NEXT) # Event code 408 (KEY_RESTART) # Event code 409 (KEY_SLOW) # Event code 410 (KEY_SHUFFLE) # Event code 412 (KEY_PREVIOUS) # 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 431 (KEY_DISPLAYTOGGLE) # Event code 432 (KEY_SPELLCHECK) # Event code 433 (KEY_LOGOFF) # Event code 439 (KEY_MEDIA_REPEAT) # Event code 442 (KEY_IMAGES) # Event code 576 (KEY_BUTTONCONFIG) # Event code 577 (KEY_TASKMANAGER) # Event code 578 (KEY_JOURNAL) # Event code 579 (KEY_CONTROLPANEL) # Event code 580 (KEY_APPSELECT) # Event code 581 (KEY_SCREENSAVER) # Event code 582 (KEY_VOICECOMMAND) # Event code 592 (KEY_BRIGHTNESS_MIN) # Event code 593 (KEY_BRIGHTNESS_MAX) # Event type 2 (EV_REL) # Event code 6 (REL_HWHEEL) # 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 c52f 0111 P: 00 00 00 00 00 00 00 00 B: 00 0b 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 5f 41 d9 fa 7b 67 00 B: 01 00 c0 17 8b 93 0f 13 00 B: 01 01 00 00 00 00 00 00 00 B: 01 00 00 00 00 46 44 54 bf B: 01 2d f3 af 17 ff ff 83 04 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 7f 00 03 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 40 00 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: 14 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 ################################ # Waiting for events # ################################ ^C[root@domek ~]# And no events on scrolling.
sorry about the delay. Benjamin, do you know why this shows up as USB receiver instead of actual device?
(In reply to Peter Hutterer from comment #23) > Benjamin, do you know why this shows up as USB > receiver instead of actual device? The receiver has a PID of C52F. We currently only bind to C532 and C52B. So that means there is a new type of receiver that needs to be added in the kernel. I'll check with Logitech.
We got the answer from Logitech, and this should not go through hid-logitech-dj. We might get more information through hid-logitech-hidpp but this will not help with the missing events. Could you attach a hid-recorder log (package hid-replay) of the device (as root) when you use the wheel?
FTR: I've been trying to contact with Logitech support and within last 3 months not been able even make any movement about have any linux to reproduce this bug. I'me rally disappointed Logitech support quality :( Few weeks ago I left my buggy mouse at my family home and after this I've purchased fresh M220 mouse, and with this one wheel is scrolling, it is proper timing on c&p on using middle button .. no issues at all. Just in case now I'm not able to reproduce this bug but within about 3 weeks will have back that buggy mouse :) My guess is that that it must be something wrong with mouse internal controller firmware and this firmware in latest versions of the Logitech devices is fixed.
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
Thomasz: do I read comment 26 right that it works now? Or is this a different device altogether? Either way, punting this off to benjamin and the kernel.
I've changed mouse. I'm no longer able to reproduce this. As Logitech support did not are I've decided to buy new non-Logitech mouse which is working. I still have few other Logitech devices but they are connected over other types of the URs. So far no problems with those devs :) Feel free to close this ticket :)
Closing as insufficient_data based on comment above.