summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Hutterer <peter.hutterer@who-t.net>2018-10-03 11:11:20 +1000
committerPeter Hutterer <peter.hutterer@who-t.net>2018-10-03 11:13:58 +1000
commit2a83357babab91f7c76de4b857bb2d3cdcffc472 (patch)
treeef0905474bb27623c205443aae7721fd096a2fa9
parentd1a0d50c30bde5742e52566ecda379b597c361e3 (diff)
downloadlibinput-2a83357babab91f7c76de4b857bb2d3cdcffc472.tar.gz
doc/user: add a warning that udevadm test doesn't always work
We rely on the udev keyboard builtin to set the fuzz but that builtin isn't run during udevadm test. So running sudo udevadm test shows the LIBINPUT_FUZZ properties the first time round (still set from boot), but not the second time. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-rw-r--r--doc/user/device-configuration-via-udev.rst5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/user/device-configuration-via-udev.rst b/doc/user/device-configuration-via-udev.rst
index eac1c409..b9ebb23b 100644
--- a/doc/user/device-configuration-via-udev.rst
+++ b/doc/user/device-configuration-via-udev.rst
@@ -247,6 +247,11 @@ in the udev rules files). ::
sudo udevadm test /sys/class/input/eventX
+.. warning:: ``udevadm test`` does not run commands specified in ``RUN``
+ directives. This affects the udev properties relying on e.g.
+ the udev keyboard builtin such as the :ref:`touchpad_jitter`
+ workarounds.
+
.. _hwdb_modifying:
..............................................................................