I've installed libinput to enable debounce. I added settings to
/etc/libinput/local-overrides.quirks. But it doesn't work.
I try to debug libinput with command
libinput debug-events --verbose and it says:
event2 - debounce state: DEBOUNCE_STATE_DISABLED → DEBOUNCE_EVENT_OTHERBUTTON → DEBOUNCE_STATE_DISABLED event2 - debounce state: DEBOUNCE_STATE_DISABLED → DEBOUNCE_EVENT_PRESS → DEBOUNCE_STATE_DISABLED event2 - debounce state: DEBOUNCE_STATE_DISABLED → DEBOUNCE_EVENT_RELEASE → DEBOUNCE_STATE_DISABLED
So debounce doesn't work and I can't understand why.
[DEXIN Tt eSPORTS THERON] MatchName=DEXIN Tt eSPORTS THERON ModelBouncingKeys=1 [DEXIN Tt eSPORTS THERON Keyboard] MatchName=DEXIN Tt eSPORTS THERON Keyboard ModelBouncingKeys=1 [DEXIN Tt eSPORTS THERON Consumer Control] MatchName=DEXIN Tt eSPORTS THERON Consumer Control ModelBouncingKeys=1 [mouse] MatchUdevType=mouse ModelBouncingKeys=1 [THERON] MatchName=*THERON* ModelBouncingKeys=1 [DEXIN] MatchName=*DEXIN* ModelBouncingKeys=1
ModelBouncingKeys=1quirk does is it says "bouncing keys for this model are, for whatever weird reason, the normal behavior" (I admit, it may not be immediately clear from the naming, I had to double-check it locally too). IIRC one such example is the virtual mouse pointer in VMWare: it slightly delays the click, and so upon double-clicking clicks get sent very close in time. FTR: when debounce is enabled, instead of
libinput debug-events --verboseimmediately, because that utility is making use of the library and you just started it. But at the same time you'll see no actual changes in mouse behavior (as opposed to entries in the
libinput-debug-eventslog) because your running Xorg/wayland-compositor are past the point they read the file, so you'll want to restart them.