Bug 468276

Summary: [feature request] Add toggle to enable or disable libinput double click prevention
Product: [Applications] systemsettings Reporter: sartamo
Component: kcm_mouseAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED UPSTREAM    
Severity: wishlist CC: duha.bugs, nate
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description sartamo 2023-04-08 09:45:26 UTC 
Situation:

libinput has a double click prevention: If the mouse debounces and clicks happen too fast after each other, they are not registered. Normally, this is a wanted behavior because people don't want to accidentally double click when the mouse is debouncing.

Request: 

There is a way to toggle this behavior by using the command line and editing /etc/libinput/local-overrides.quirks (described in https://askubuntu.com/questions/1199820/how-to-disable-mouse-debouncing-in-libinput). Add this as a graphical toggle in the mouse settings.

Why this is important: 

There are multiple scenarios where you need double clicks from debounces to be registered (take "godbridging" in minecraft as an example).  With KDE's vision to give the user the choice, there should be a graphical setting in the mouse configuration module to configure this behavior: The reason to why clicks don't happen as fast is not obvious to newcomers and the solution can take a lot of research to be discovered. But they might look into the graphical mouse settings to find a solution.
Comment 1 Nate Graham 2023-04-10 18:00:02 UTC 
I'm afraid we can't support this by editing the quirks file; that file is distro-provided, and any edits we make to it will be overridden on the next system upgrade. We'll need for Libinput to natively support disabling this behavior via a supported API before we can expose it to the users.

An even better solution would be to fix the bug in Libinput so no configurability is required. I would recommend submitting a bug report for Libinput that demonstrates how the issue affects you.