bug #932439 seems similar to this one, although that only sprang up recently (since moving to 1.12), so not sure it is directly a dupe.
The same workaround probably works here:
xinput set-button-map <device-number> 1 2 3 4 5 7 6
Use 'xinput list' to figure out what your mouse's device number is.
bug #932439 seems similar to this one, although that only sprang up recently (since moving to 1.12), so not sure it is directly a dupe.
The same workaround probably works here:
xinput set-button-map <device-number> 1 2 3 4 5 7 6
Use 'xinput list' to figure out what your mouse's device number is.