So I tried looking through the various other questions but they mostly focus on disabling the middle mouse paste.

Basically the middle mouse button on my Logitech G500s is broken, and it keeps "clicking" randomly so it's screwing up any chance of doing work.

Is there any way to disable it? Or map it to nothing?

Thanks and sorry if this is a duplicate.

xinput list output:

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜   ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜   ↳ Turtle Beach Turtle Beach PX3 (XBOX) id=8 [slave pointer (2)]
⎜   ↳ Logitech G500s Laser Gaming Mouse id=9 [slave pointer (2)]
⎜   ↳ Logitech G500s Laser Gaming Mouse id=10 [slave pointer (2)]
⎜   ↳ Razer Razer DeathStalker id=12 [slave pointer (2)]
⎜   ↳ Razer Razer DeathStalker id=13 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Power Button id=7 [slave keyboard (3)]
    ↳ Razer Razer DeathStalker id=11 [slave keyboard (3)]
  • Execute this command xinput list | grep 'id=' and post the output. – 0x2b3bfa0 Mar 15 '15 at 13:36
  • For this mouse, there are two device ID's for this mouse. After running xinput test 9, the id of my mouse middle button is 2 – Tom Hamilton Stubber Mar 15 '15 at 13:42

Execute those commands:

xinput set-button-map 9 1 0 3
xinput set-button-map 10 1 0 3

Explanation (kindly donated by @Yehosef):

The first number is the identifier of the pointer (you'll often only have one, in this case there were two, 9 and 10).

The next numbers are what you do with the first, second, and third (ie, left, middle, right) mouse buttons. 1 0 3 tells it that the left button should do a left click (action 1), the middle button should do nothing, and the right button should do a right click (action 3). If you want to make the middle button also do a left click you could use 1 1 3. If you wanted to switch the right and left actions you could use 3 0 1. See https://wiki.ubuntu.com/X/Config/Input for more info.

| improve this answer | |
  • Thanks a lot, trying to look this up was getting very frustrating. – Tom Hamilton Stubber Mar 15 '15 at 13:46
  • 1
    Thanks! For those wondering - the 9/10 are the input id of the mouse and the 1 0 3 are the mappings for the first, second, and third mouse buttons. If you wanted all buttons to do the same thing you could use 1 1 1 or if you want to switch the right and left buttons you could use 3 0 1. – Yehosef Jul 26 '16 at 8:03
  • @Yehosef: Thanks! I did not explain what is happening when the OP ran the commands. Please create a new detailed answer, ping me and I'll upvote. This is an interesting explaination. – 0x2b3bfa0 Jul 26 '16 at 20:13
  • @Helio I don't have a different answer - just more explanation for those interested. Perhaps you want to edit your answer to include this info you can. I was thinking about editing your answer - but I generally don't like it when people add extra details to my answers - so I refrained :) – Yehosef Jul 27 '16 at 11:15
  • 3
    So how do I determine the first number. I run xinput list | grep 'id=' and look for the things that looks most like my mouse/touchpad? Any definitive way of telling whether it is the right one? – Kvothe Jul 24 '18 at 21:15

Following instructions are based on info at Ubuntu Wiki (Scroll down to title "Example: Disabling middle-mouse button paste on a scrollwheel mouse").

First, determine id of the pointer by listing input devices:

xinput list | grep 'id='

And look for the line that contains name of your pointer, there also should be id of the device, right after "id=". For example, id of this device is 10:

Lenovo ThinkPad Compact USB Keyboard with TrackPoint    id=10   [slave  pointer  (2)]

Next, get current button map of that device (I'll be using id of my device, which is 10):

xinput get-button-map 10


1 2 3 4 5 6 7 8 9

This is mapping of pointer buttons to actions, where number represents action code, and position - button.

We're interested in second map - number 2 corresponds to action "Middle Button Click" and the position of it - to actual middle button.

To disable middle button triggering any action, I'd use command xinput set-button-map with id of the device and updated map (new action code is 0 - no action). No need to put whole map - map till interested button suffice (the rest just won't be updated):

 xinput set-button-map 10 1 0

That's it.

| improve this answer | |
  • This worked for my touchpad on a Lenovo Thinkpad T580 with Ubuntu 18.04 – Russell England Apr 24 '19 at 8:34
  • 2
    I think this answer is more thorough as it's important information to be able to get the id number of the input device. Otherwise, you're just randomly changing device settings. – Eric Streeper Jun 5 at 22:15
  • Also - if you don't want the middle third of the click area to perform no action, you might want to consider setting it to left-click, so the left two thirds perform a left click, like xinput set-button-map X 1 1 – ACK_stoverflow Oct 22 at 1:58

set-button-map disables middle click functionality. To emulate middle-click using left+right click (so you can paste and open-in-tab etc using the mouse) but disable mouse wheel clicks, you can patch libinput:

--- a/src/evdev.c   2019-09-22 17:15:13.498880044 +0300
+++ a/src/evdev.c   2019-09-22 17:15:18.062860221 +0300
@@ -1861,6 +1861,8 @@
    /* Logitech Marble Mouse claims to have a middle button */
    if (device->model_flags & EVDEV_MODEL_LOGITECH_MARBLE_MOUSE)
        libevdev_disable_event_code(device->evdev, EV_KEY, BTN_MIDDLE);
+   libevdev_disable_event_code(device->evdev, EV_KEY, BTN_MIDDLE);

 static void
  • mkdir deb; cd deb; apt source libinput; sudo apt build-dep libinput
  • save the above patch as libinput-1.XX.Y/debian/patches/middle.diff
  • add middle.diff to debian/patches/series
  • dpkg-buildpackage -us -uc -b
  • sudo dpkg -i ../libinput10_*.deb
  • restart Xorg or restart the machine

And use xinput list and xinput set-prop 11 "libinput Middle Emulation Enabled" 1 to enable the left+right emulation. 11 is the device number from xinput list and you can add the set-prop command to ~/.xstartup.

Or, to to avoid rebuilding, use a libinput .quirks file (untested):

[My Mouse]
| improve this answer | |

This is what I do on Ubuntu 20.04 (uses Wayland by default) to disable my middle button or remap my middle button.

To find my device id:

$ xinput --list
⎡ Virtual core pointer                      id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ xwayland-pointer:17                       id=6    [slave  pointer  (2)]
⎜   ↳ xwayland-relative-pointer:17              id=7    [slave  pointer  (2)]
⎜   ↳ xwayland-touch:17                         id=9    [slave  pointer  (2)]
⎣ Virtual core keyboard                     id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ xwayland-keyboard:17                      id=8    [slave  keyboard (3)]

I had to do a couple test before I found the right id. For me, it was 6.

To see current button map:

$ xinput get-button-map 6
1 2 3 4 5 6 7 8 9 10 

To disable middle button:

$ xinput set-button-map 6 1 0 3 4 5 6 7 8 9 10

To remap middle button to left click:

$ xinput set-button-map 6 1 1 3 4 5 6 7 8 9 10

In order to run at startup, create a file and make sure it's executable (chmod a+x):

xinput set-button-map 6 1 1 3 4 5 6 7 8 9 10

Ubuntu and other GNOME based distributions come with an application simply called “Startup Applications”. It can be used for managing apps and scripts that run on a fresh system reboot or login. So just do a search for it, open it and add the file you just created.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.