Discovered this problem yesterday, which led me to this bug-report: Middle-button clicking was dead and didn't work on a clean new xenial install, same mouse works fine on an upgraded PC.
Testing with xev showed nothing on the new PC: Middle button clicks were not recognised. "xinput list" told the mouse was: "PixArt HP USB Optical Mouse id=1 [slave pointer (2)] Ran a few "xinput test <ID>" commands. (NOT only on the mouse's ID (15) but a another to initially, lower number, typo.) And alas: Middle button clicks were suddenly detected and worked like charm - for half an hour. Then it died again. I repeated the "xinput test" deal, now on several ID's, lastly the mouse. After this, the middle button clicks were once again detected. This time i rebooted the PC, power-pff/on. Wheel-clicking survived the reboot and still works, 36 hours later or so. I'm not a kernel person but as an old-time user I got a little back-flash to the days of kernel 2.0, when devices often had to be added and linked manually. A look in /dev revealed several recent changes, from the time of the xinput tests. Grep'ed around and found: me@pc:/dev$ ls -latr |grep "11:48" drwxr-xr-x 4 root root 520 Dec 16 11:48 input drwxr-xr-x 21 root root 4200 Dec 16 11:48 . crw------- 1 root root 247, 0 Dec 16 11:48 hidraw0 drwxr-xr-x 2 root root 4140 Dec 16 11:48 char me@pc:/dev/input$ ls -latr |grep "11:48" drwxr-xr-x 21 root root 4200 Dec 16 11:48 .. drwxr-xr-x 4 root root 520 Dec 16 11:48 . crw-rw---- 1 root input 13, 34 Dec 16 11:48 mouse2 crw-rw---- 1 root input 13, 80 Dec 16 11:48 event16 drwxr-xr-x 2 root root 220 Dec 16 11:48 by-path drwxr-xr-x 2 root root 100 Dec 16 11:48 by-id me@pc:/dev/input/by-path$ ls -latr |grep "11:48" drwxr-xr-x 4 root root 520 Dec 16 11:48 .. lrwxrwxrwx 1 root root 9 Dec 16 11:48 pci-0000:00:14.0-usb-0:1:1.0-mouse -> ../mouse2 lrwxrwxrwx 1 root root 10 Dec 16 11:48 pci-0000:00:14.0-usb-0:1:1.0-event-mouse -> ../event16 me@pc:/dev/input/by-id$ drwxr-xr-x 4 root root 520 Dec 16 11:48 .. lrwxrwxrwx 1 root root 9 Dec 16 11:48 usb-PixArt_HP_USB_Optical_Mouse-mouse -> ../mouse2 lrwxrwxrwx 1 root root 10 Dec 16 11:48 usb-PixArt_HP_USB_Optical_Mouse-event-mouse -> ../event16 drwxr-xr-x 2 root root 100 Dec 16 11:48 . me@pc:/dev/char$ lrwxrwxrwx 1 root root 18 Dec 16 11:48 189:8 -> ../bus/usb/001/009 lrwxrwxrwx 1 root root 10 Dec 16 11:48 247:0 -> ../hidraw0 lrwxrwxrwx 1 root root 15 Dec 16 11:48 13:34 -> ../input/mouse2 lrwxrwxrwx 1 root root 16 Dec 16 11:48 13:80 -> ../input/event16 Hoping the listings above can be of help in solving this annoyance. I agree "Importance" should be raised to major. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581088 Title: Middle mouse (wheel-click) button stopped working after upgrade to 16.04 Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 16.04 clicking the middle mouse button (scroll wheel) on my Logitech M185 stopped working. xev does not even show the event for clicking the wheel, while it shows other button clicks and scroll wheel up/down events. xinput list shows the USB receiver 2 times: ⎡ 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)] ⎜ ↳ Logitech USB Receiver id=10 [slave pointer (2)] ⎜ ↳ HID 046a:0023 id=13 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=16 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=17 [slave pointer (2)] Listing the capabilities looks like this: $ xinput list 9 Logitech USB Receiver id=9 [slave pointer (2)] Reporting 7 classes: Class originated from: 9. Type: XIButtonClass Buttons supported: 24 Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" Button state: Class originated from: 9. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.000000 - -1.000000 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.000000 - -1.000000 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.000000 - -1.000000 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 3: Label: Rel Vert Wheel Range: -1.000000 - -1.000000 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.000000 flags: 0x0 Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 3 type: 1 (vertical) increment: -1.000000 flags: 0x2 ( preferred ) $ xinput list 10 Logitech USB Receiver id=10 [slave pointer (2)] Reporting 6 classes: Class originated from: 10. Type: XIButtonClass Buttons supported: 7 Button labels: "Button 0" "Button Unknown" "Button Unknown" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" Button state: Class originated from: 10. Type: XIKeyClass Keycodes supported: 248 Class originated from: 10. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.000000 - -1.000000 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.000000 - -1.000000 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.000000 - -1.000000 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.000000 flags: 0x0 Does anyone have an idea how I can attempt to further debug that issue? Or maybe even a solution? Should I consider this issue a bug? Can I provide more info? --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: toby 11625 F.... pulseaudio /dev/snd/controlC0: toby 11625 F.... pulseaudio /dev/snd/pcmC1D0p: toby 11625 F...m pulseaudio /dev/snd/controlC1: toby 11625 F.... pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5e3a6d2e-05f8-4d01-b80c-a9f8888200e6 InstallationDate: Installed on 2014-04-24 (749 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: LENOVO 20AL00C6GE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=82920e97-9472-4bf4-95d3-3b07ae5eb747 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware 1.157 Tags: xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-05-02 (9 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 03/25/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GIET72WW (2.22 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AL00C6GE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET72WW(2.22):bd03/25/2014:svnLENOVO:pn20AL00C6GE:pvrThinkPadX240:rvnLENOVO:rn20AL00C6GE:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AL00C6GE dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
