Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • The only other way I can think of to check the button's input is with xbindkeys -k. Might be worth a shot. Commented Sep 24 at 21:11
  • This only detects keys for me and doesn't reject to any mouse or touchpad I tried. Commented Sep 25 at 11:02
  • s/reject/react/ Commented Sep 25 at 11:08
  • What does xinput say? Run xinput and get the mouse Device ID. Then, xinput test [device ID]. If you still have nothing, it's likely window manager/compositor settings that has control of mouse button behavior, preventing "grabbing". If the mouse is using /dev/input/mice you can use cat /dev/input/mice to check the button for a response. It output's a bunch of gibberish, but will show something if the button responds. Commented Sep 25 at 14:25
  • It's the same with xinput: movement – motion a[0]=319, left mouse button – button press 1 button release 1, right mouse button – button press 3 button release 3, middle mouse button – nothing. Commented Oct 2 at 21:39