diff options
author | Peter Hutterer <peter.hutterer@who-t.net> | 2020-03-21 21:09:50 +1000 |
---|---|---|
committer | Peter Hutterer <peter.hutterer@who-t.net> | 2020-04-11 09:07:11 +1000 |
commit | ce1c4c5008c7077d4ffe2cb751b1ebecdf72a42f (patch) | |
tree | c6ff61910efb8be29a965cd57ee461156435c645 | |
parent | aec607ecb4c3d07b680f9d4f66d57fa73d53e612 (diff) | |
download | libinput-ce1c4c5008c7077d4ffe2cb751b1ebecdf72a42f.tar.gz |
doc: update the jumping cursor docs
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
(cherry picked from commit 150f5dc8016fbcaf1db202eefc1cf72892b312dc)
-rw-r--r-- | doc/user/touchpad-jumping-cursors.rst | 17 |
1 files changed, 11 insertions, 6 deletions
diff --git a/doc/user/touchpad-jumping-cursors.rst b/doc/user/touchpad-jumping-cursors.rst index 50df6715..f1c49d74 100644 --- a/doc/user/touchpad-jumping-cursors.rst +++ b/doc/user/touchpad-jumping-cursors.rst @@ -17,10 +17,10 @@ the text **"Touch jump detected and discarded."** and a link to this page. .. note:: This warning is ratelimited and will stop appearing after a few times, even if the touchpad jumps continue. -In most cases, this is a bug in the kernel driver and to libinput it appears -that the touch point moves from its previous position. The pointer jump can -usually be seen in the :ref:`libinput record <libinput-record>` output for the device: - +In most cases, this is a bug in the firmware (or kernel driver) and to +libinput it appears that the touch point moves from its previous position. +The pointer jump can usually be seen in the :ref:`libinput record +<libinput-record>` output for the device: :: @@ -53,9 +53,14 @@ usually be seen in the :ref:`libinput record <libinput-record>` output for the d In this recording, the pointer jumps from its position 3752/2216 to 1640/4681 within a single frame. On this particular touchpad, this would represent a physical move of almost 50mm. libinput detects some of these -jumps and discards the movement but otherwise continues as usual. However, -the bug should be fixed at the kernel level. +jumps and discards the movement but otherwise continues as usual. +If your only encounter with these jumps is the warning printed to the log, +libinput functions as intended. When you encounter the warning in the log, please generate a recording of your touchpad with :ref:`libinput record <libinput-record>` and file a bug. See :ref:`reporting_bugs` for more details. + +Note that it most cases, libinput cannot actually fix the issue. Filing a +bug is useful to figure out if there are other factors at play or whether +there are heuristics we can employ to reduce the impact. |