I have a Logitech MX-510, that I've been using for about six years.The Mouse has several extra buttons, that I'd like to use in Gnome, but I have problems with the button codes, that the mouse sends to the driver:Button 1 (mouse wheel button) works as expected. One ButtonPress event with state 0x10 and button 1 on press, and ButtonRelease with state 0x110on release.Button 2 (mouse wheel button) works as expected. One ButtonPress event with state 0x10 and button 2 on press, and ButtonRelease with state 0x210on release.Button 3 (right button) works as expected. One ButtonPress event with state 0x10 and button 3 on press, and ButtonRelease with state 0x410on release.Button 4 (scroll up) works as expected. It sends a ButtonPress event with state 0x10 and button 4, and a ButtonRelease event with state 0x810. Both events occur instantaneous on each scroll step.Button 5 (scroll down) works as expected. It sends a ButtonPress event with state 0x10 and button 5, and a ButtonRelease event with state 0x1010. Both events occur instantaneous on each scroll step.Buttons 6 and 7 seem to not exist.Button 8 (back button) works as expected. It sends a ButtonPress event with state 0x10 and button 8, and a ButtonRelease event also with state 0x10. Both events occur instantaneous on each scroll step.Button 9 (back button) works as expected. It sends a ButtonPress event with state 0x10 and button 9, and a ButtonRelease event also with state 0x10. Both events occur instantaneous on each scroll step.The mouse has three additional buttons, as you can see in the picture above.Button 10 (on the very top of the mouse) is not usable. It sends a ButtonPress event with state 0x10 and button 10, and a ButtonRelease event also with state 0x10. The button is not usable with Gnome, because it is not selectable. Most option selectors, like that one of CompizConfig Settings Manager just goes up to Button 9.Button 11 (extra button to the front of the mouse wheel) is not quite usable. When pressed, it sends a ButtonPress event with state 0x10 and button 11, and another ButtonPress event with state 0x10 and button 4 and yet another one ButtonPress event with state 0x810 and button 4 (the last two being the same behaviour as if the scroll wheel was moved one step up). On release it sends a ButtonRelease event with state 0x10 and button 11. But the catch is, when the button is held down, it repeats the mouse wheel simulation about five times per second. (like a mousewheel cruise-control or something).Button 12 (extra button to the back of the mouse wheel) is not quite usable. When pressed, it sends a ButtonPress event with state 0x10 and button 12, and another ButtonPress event with state 0x10 and button 5 and yet another one ButtonPress event with state 0x1010 and button 5 (the last two being the same behaviour as if the scroll wheel was moved one step up). On release it sends a ButtonRelease event with state 0x10 and button 12. When held down it displays the same cruise-control behavior as button 11, but with the respective button and state parameters.Is there a way how I can remap those additional keys in a way, where I can use them or make them usable with Gnome? And especially, if it is possible, to make buttons 11 and 12 stop sending codes for mouse wheel scroll up and down.And if possible, how can I change the general behavior of the mouse buttons in general?
Logitech MX-510: Some extra buttons not usable
fedora;gnome;mouse