When reporting bugs against libinput, you will need:
- a reliable :ref:`reproducer <reporting_bugs_reproducer>` for the bug
-- an :ref:`evemu recording <evemu>` of the device while the bug is reproduced
+- a :ref:`recording <libinput-record>` of the device while the bug is reproduced
- device-specific information, see
- :ref:`reporting_bugs_touchpad`
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 evemu-record output for the device:
+usually be seen in the :ref:`libinput record <libinput-record>` output for the device:
::
jumps and discards the movement but otherwise continues as usual. However,
the bug should be fixed at the kernel level.
-When you encounter the warning in the log, please generate an evemu
-recording of your touchpad and file a bug. See :ref:`reporting_bugs` for more
-details.
+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.
AttrTouchSizeRange=10:8
The first line is the match line and should be adjusted for the device name
-(see evemu-record's output) and for the local system, based on the
+(see :ref:`libinput record <libinput-record>`'s output) and for the local system, based on the
information in ``/sys/class/dmi/id/modalias``. The modalias should be
shortened to the specific system's information, usually system vendor (svn)
and product name (pn).