| Summary: | The touchpad disable/enable functionality does not work by double tapping on the LED zone in the upper left corner | ||
|---|---|---|---|
| Product: | Wayland | Reporter: | Alexey Svistunov <svalx> |
| Component: | libinput | Assignee: | Wayland bug list <wayland-bugs> |
| Status: | RESOLVED MOVED | QA Contact: | |
| Severity: | minor | ||
| Priority: | medium | CC: | peter.hutterer, svalx |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| See Also: | https://bugs.freedesktop.org/show_bug.cgi?id=39055 | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Alexey Svistunov
2018-04-06 07:57:00 UTC
Does the kernel expose the LED? without that, we can't really do much. And the next problem is going to be write access to the LED which we're unlikely to get unless we're root. No, the LED is not exposed by the kernel, /sys/class/leds/psmouse::synaptics/ is absent. But there is a patch (https://aur.archlinux.org/packages/synaptics-led/) for the psmouse module in Arch Linux, which adds this. I do not have enough skills to submit it to the kernel. hmm, so it comes down to: we can't merge this in libinput until we figure out how the LED behaves. And that requires the kernel patch to be merged upstream. Magically disabling the touchpad with no feedback to the user is not something I want to do, I get enough angry emails already. Also note that we've been slowly switching synaptics touchpads in the kernel to SMBus/RMI4 where possible so that LED patch would likely have to work for that too. Closing this bug for now, please re-open when the kernel solution is in place. The libinput bit isn't that hard to write. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.