Changing/Disabling Third Mouse Button in Plasma

[vtpoet]

My problem: I've got a nice little Logitech Bluetooth mouse. The problem I'm having is that the surface of the mouse accepts Touch Gestures:

https://www.amazon.com/Logitech-Ultr...luetooth+mouse

This is becoming very problematic in Plasma. Every time my finger dithers on the mouse in the wrong way, I end up pasting the clipboard contents into my document: over and over and over again.

Is there a setting in Plasma to change or disable the third mouse button?

[oshunluvr]

Maybe it's detected as a touchpad? Try turning touchpad off in system settings.

[vtpoet]

Maybe it's detected as a touchpad? Try turning touchpad off in system settings.

Good suggestion, but it didn't work. The problem though is that the touch surface of the mouse also allows me to scroll.

[oshunluvr]

Well, I wish I knew an easy answer. First - search the Arch wiki to see if anyone over there has configured your mouse. Their wiki is quite detailed and written by experts. If anyone can figure it out, someone over there will.

If no joy there, start by determining what keycodes are generated by the actions. You use "xev" for that. Run xev in a terminal, put the mouse pointer over the xev box and start gesturing. The terminal will scroll a BUNCH of stuff but you'll be looking for similar output to this:

[FONT=monospace][COLOR=#000000]ButtonPress event, serial 41, synthetic NO, window 0x5e00001,[/COLOR]
    root 0x2a9, subw 0x5e00002, time 345658038, (37,42), root:(223,71),
    state 0x0, button 1, same_screen YES

EnterNotify event, serial 41, synthetic NO, window 0x5e00001,
    root 0x2a9, subw 0x0, time 345658038, (37,42), root:(223,71),
    mode NotifyGrab, detail NotifyInferior, same_screen YES,
    focus YES, state 256

KeymapNotify event, serial 41, synthetic NO, window 0x0,
    keys:  1   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0    
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0    
[/FONT]

Note where it says "button 1". Each gesture may give a button number or a key code. Key codes look like:

[FONT=monospace][COLOR=#000000]KeyPress event, serial 40, synthetic NO, window 0x4c00001,[/COLOR]
    root 0x2a9, subw 0x0, time 346063781, (71,55), root:(71,84),
    state 0x0, keycode 42 (keysym 0x67, g), same_screen YES,
    XLookupString gives 1 bytes: (67) "g"
    XmbLookupString gives 1 bytes: (67) "g"
    XFilterEvent returns: False

KeyRelease event, serial 40, synthetic NO, window 0x4c00001,
    root 0x2a9, subw 0x0, time 346063997, (71,55), root:(71,84),
    state 0x0, keycode 42 (keysym 0x67, g), same_screen YES,
    XLookupString gives 1 bytes: (67) "g"
    XFilterEvent returns: False

[/FONT]

Here you'll find "keycode XX". Once you figure out what buttons or keycodes are being used, you can re-map them to null or some other function.