Middle mouse (wheel) button stopped working after upgrade to 16.04

Asked by tobyS

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?

Question information

Language:
English Edit question
Status:
Open
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

If you run:

xev

Does the button make events?

Revision history for this message
tobyS (tobias-schlitt) said :
#2

Thanks for your reply.

xev does note events for left/right-click as well als wheel-up/down, but it does not note any events for wheel click.

Revision history for this message
Guntbert Reiter (guntbert) said :
#3

The exact same (with a different mouse model: ELECOM WIRELESS LASER MOUSE) happens here. I'd suggest to open a bug instead of a question.

Revision history for this message
tobyS (tobias-schlitt) said :
#4

@Guntbert: Thanks for your input. While the behavior is annoying I'm happy to find someone else affected. I'll open a bug from the question.

Revision history for this message
tobyS (tobias-schlitt) said :
#5

Can you help with this problem?

Provide an answer of your own, or ask tobyS for more information if necessary.

To post a message you must log in.