unable to remap mouse buttons

[Jamin W. Collins]

Binary package hint: xinput

Intrepid no longer uses xorg.conf for input definitions (from everything I can gather), but now relies on information from hal. However, hal currently doesn't honor the button remapping [https://help.ubuntu.com/community/Logitech_Marblemouse_USB#Middle%20Click]. So, xinput should allow for the remapping of the buttons. As far as I can tell, I'm executing the command as I should, but it is failing:

xinput set-button-map "BELKIN MOUSE" 1 8 3
X Error of failed request: BadValue (integer parameter out of range for operation)
  Major opcode of failed request: 148 (XInputExtension)
  Minor opcode of failed request: 29 (X_SetDeviceButtonMapping)
  Value in failed request: 0x8
  Serial number of failed request: 13
  Current serial number in output stream: 13

The only way I've been able to remap the buttons at this point is via xmodmap, but it changes the mapping for all of the attached mice which is less than desirable.

[Rob Hubble (rob-hubble)]

In my experience, you must remap all buttons that are currently mapped when using xinput. You're only trying to remap the first 3 buttons. Try 1 8 3 4 5 6 7 2 9 ? Or something similar?

[Jamin W. Collins (jcollins)]

I've tried it both ways, end result is the same either way, the command errors.

[Bryce Harrington (bryce)]

Hi jcollins,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISO CD images are available from http://cdimage.ubuntu.com/releases/)

If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jamin W. Collins (jcollins)]

Just tested it with current Jaunty and it appears to be working correctly. Not sure when it was corrected though.