Summary: | Is there any way to disable palm detection? | ||
---|---|---|---|
Product: | Wayland | Reporter: | 90fve0+43ldlc5hx6vy0 |
Component: | libinput | Assignee: | Wayland bug list <wayland-bugs> |
Status: | RESOLVED INVALID | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
90fve0+43ldlc5hx6vy0
2017-11-07 07:33:13 UTC
I need more info please I'm trying to find out how to disable palm detection as described here: https://wayland.freedesktop.org/libinput/doc/latest/palm_detection.html While the palm exclusion zones behave as described in the documentation they have an extremely high false positive rate for me. Thank you for your help. there's no toggle to turn those off (other than dwt). We generally try to focus on fixing the issues that users have so it works without needing user-specific configuration. What version of libinput are you on, what laptop do you have, etc. See https://wayland.freedesktop.org/libinput/doc/latest/reporting_bugs.html for a list of what we'll probably need to debug this. Sorry, I'll try to do a better job of explaining the issue. By false positive I mean that I try to click or move the pointer but libinput ignores it because the tap started in an exclusion zone. I find myself tapping in an exclusion zone frequently. It is very frustrating to have my taps ignored and to not be able to use the full area of my touchpad. I did not include debugging information because according to https://wayland.freedesktop.org/libinput/doc/latest/palm_detection.html this behavior is intentional. If it is not currently possible to disable palm detection then I suggest adding the option to do so for people who prefer the reliability of being able to use the entire touchpad over minimizing palm clicks. please see https://wayland.freedesktop.org/libinput/doc/latest/faq.html#faq_configuration and I still need the various bits and pieces to debug this further, thanks. There is nothing to debug. The palm exclusion zones are doing what the documentation says that they are supposed to do. I find this behavior undesirable and I'm looking for a way to turn palm detection off. In other words I would like to make my whole touchpad behave the way the gray region of the picture does here: https://wayland.freedesktop.org/libinput/doc/latest/palm_detection.html Since there is apparently no way to disable palm detection with gsettings the way there is for natural-scroll, tap-to-click, etc. I'm forced to choose between 1. putting up with a touchpad that ignores about 1/4 of deliberate actions because they started in an exclusion zone, 2. attempt (and probably fail) to modify libinput and recompile from source or 3. switch to a distro that does not use libinput. ok, sounds like you have your mind made up, so I'm closing this bug as WONTFIX, we have no plans to expose a toggle for this. When you're willing to have an actual discussion about this to see if there's a proper fix for it, please open a new bug. What do you mean by "proper fix"? The edge zones are supposed to be small enough that on most devices it's unlikely you're tapping exactly in that zone provided the touchpad ranges are set up correctly. That's just one example, but it's hard to figure anything out without information. +------------------------------------------------------+ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | L | | R | | | | | | | | | | | | | | | | | | |----------------------------------------| | | | B | | | | | | +------------------------------------------------------+ The exclusion zones cover %38 of the total touchpad area. total touchpad size = 105mm x 64mm left exclusion zone = 14mm x 64mm right exclusion zone = 14mm x 64mm bottom exclusion zone = 77mm x 10mm The bottom exclusion zone allows taps but prevents horizontal motion if the touch started in the zone. I have a System76 Kudu3 laptop running Ubuntu 17.10. The touchpad has physical buttons underneath the touch surface, not separate from it. xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ xwayland-pointer:13 id=6 [slave pointer (2)] ⎜ ↳ xwayland-relative-pointer:13 id=7 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ xwayland-keyboard:13 id=8 [slave keyboard (3)] udevadm info /sys/class/input/event6 P: /devices/platform/i8042/serio2/input/input10/event6 N: input/event6 E: DEVNAME=/dev/input/event6 E: DEVPATH=/devices/platform/i8042/serio2/input/input10/event6 E: ID_BUS=i8042 E: ID_INPUT=1 E: ID_INPUT_HEIGHT_MM=57 E: ID_INPUT_TOUCHPAD=1 E: ID_INPUT_TOUCHPAD_INTEGRATION=internal E: ID_INPUT_WIDTH_MM=97 E: LIBINPUT_DEVICE_GROUP=11/2/7/1b1:isa0060/serio2 E: LIBINPUT_MODEL_SYNAPTICS_SERIAL_TOUCHPAD=1 E: MAJOR=13 E: MINOR=70 E: SUBSYSTEM=input E: USEC_INITIALIZED=19461567 sigh. 8 comments and 3 weeks later I'm still waiting for information requested in comment 2, closing. See comment 10. Your device has incorrect resolutions set, please run the touchpad-edge-detector and attach the full output here, thanks. ping Needinfo for 2 weeks, closing |
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.