Bug 495643

Summary: Unable to turn off tap to click on surface laptop studio 2
Product: [Applications] systemsettings Reporter: kam03m
Component: kcm_touchpadAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED UPSTREAM    
Severity: normal CC: duha.bugs, natalie_clarius, nate
Priority: NOR    
Version First Reported In: 6.2.2   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description kam03m 2024-10-31 14:55:42 UTC
SUMMARY
Thank you for implementing tap to click on touchpads recently. I use it with my apple magic touchpad. I have to restart after changing the tap to click setting before it applies but that isn't a big deal.


The problem is with the surface. I have tried with both KDE Neon and Silverblue Aurora latest. In both cases I am unable to turn off tap to click on the surface. I tried applying, resetting, etc, but the tap to touch does not turn off. I can turn it off with gnome (Ubuntu LTS) so I know it is possible with the surface hardware and surface kernel. 

STEPS TO REPRODUCE
1. Install KDE Neon on a ms surface laptop and update. (Surface laptop studio 2 was tested.)
2. Install linux surface kernel and reboot.
3. Observe that everything works as it should besides the tap to click toggle
4. Navigate to touchpad settings in system settings
5. Uncheck Tap-to-click checkbox and apply
6. Notice that tap to click is still functional.
7. Restart
8 Notice tap to click is still functional and the checkbox is still unchecked in the settings

OBSERVED RESULT
Tap to click is still functional

EXPECTED RESULT
Tap to click should be turned off when the checkbox is unchecked


SOFTWARE/OS VERSIONS
KDE neon 6.2
KDE Plasma Version: 6.2.2
Qt Version: 6.7.2
Kernel Version: 6.10.10-surface-1 (64-bit)
Graphics Platform: Wayland
Processors: 20 x 13th Gen Intel Core i7-13700H
Memory: 62.6 GiB of RAM
Graphics Processor: Mesa Intel Graphics

ADDITIONAL INFORMATION
(also tested with 6.11.X-surface kernel on Silverblue Aurora)
Comment 1 Nate Graham 2024-11-01 16:55:12 UTC
I think there may be a Libinput-specific override for this, or a bug. Can you follow up with Libinput first at https://gitlab.freedesktop.org/libinput/libinput/-/issues? If they say it's our bug, we can re-open this and investigate it.

Thanks a lot!