Lines Matching full:libinput

7 libinput provides a ``libinput`` tool to query state and events. This tool
9 explanation of the various commands available in the libinput tool is
10 available in the **libinput(1)** man page.
14 - ``libinput list-devices``: to list locally available devices as seen by libinput,
15   see :ref:`here <libinput-list-devices>`
16 - ``libinput list-kernel-devices``: to list locally available devices as seen by the kernel,
17   see :ref:`here <libinput-list-kernel-devices>`
18 - ``libinput debug-events``: to monitor and debug events,
19   see :ref:`here <libinput-debug-events>`
20 - ``libinput debug-gui``: to visualize events,
21   see :ref:`here <libinput-debug-gui>`
22 - ``libinput record``: to record an event sequence for replaying,
23   see :ref:`here <libinput-record>`
24 - ``libinput measure``: measure properties on a kernel device,
25   see :ref:`here <libinput-measure>`
26 - ``libinput analyze``: analyse event recordings from a kernel device,
27   see :ref:`here <libinput-analyze>`
28 - ``libinput quirks``: show quirks assigned to a device, see
29   :ref:`here <libinput-quirks>`
37 libinput list-devices
40 The ``libinput list-devices`` command shows information about devices
41 recognized by libinput and can help identifying why a device behaves
46           libinput built-in defaults.
50      $ sudo libinput list-devices
70 ``libinput list-devices`` command lists general information about the device
84 libinput list-kernel-devices
87 The ``libinput list-kernel-devices`` command shows the devices known by **the
89 libinput.
93     $ libinput list-kernel-devices
107     $ libinput list-kernel-devices --hid
133 libinput debug-events
135 The ``libinput debug-events`` command prints events from devices and can help
138      $ sudo libinput debug-events --enable-tapping --set-click-method=clickfinger
143 on or off as required. See the **libinput-debug-events(1)** man page or the
147           additional information: ``libinput debug-events --verbose <other options>``
151      $ sudo libinput debug-events --enable-tapping --set-click-method=clickfinger
183 libinput debug-gui
188 gathers data directly from libinput, it is thus suitable for
192           libinput built-in defaults.
196      $ sudo libinput debug-gui --enable-tapping
199 As with :ref:`libinput-debug-events`, all options must be specified on the
201 See the **libinput-debug-gui(1)** man page or the ``--help`` output for information about
207 libinput record and libinput replay
210 .. note:: For libinput versions 1.10 and older, use :ref:`evemu`.
212 The ``libinput record`` command records the **kernel** events from a specific
213 device node. The recorded sequence can be replayed with the ``libinput
217 .. graphviz:: libinput-record.gv
221 libinput context. libinput does not need to be running, it does
223 version of libinput is currently running.
228      $ sudo libinput record > touchpad.yml
252 Without arguments, ``libinput record`` displays the available devices and lets
256 the **libinput-record(1)** man page.
258 .. note:: When reproducing a bug that crashes libinput, run inside ``screen`` or
262 For data protection, ``libinput record`` obscures key codes by default, any
269 The recording can be replayed with the ``libinput replay`` command: ::
271      $ sudo libinput replay touchpad.yml
276 ``libinput replay`` creates a new virtual device based on the description in
284 More arguments are available, see the **libinput-record(1)** and
285 **libinput-replay(1)** man pages.
290 libinput record's autorestart feature
293 ``libinput record`` often collects thousands of events per minute. However,
294 the output of ``libinput record`` usually needs to be visually inspected
299 ``libinput record --autorestart=2 --output-file=recording.yml``.
307 - run ``libinput record --autorestart=2 --output-file=<somefilename>.yml``.
313 - Ctrl+C the ``libinput record`` process without using the device
316 If you have to use the recorded device to stop ``libinput record`` (e.g. to
332 ``libinput record`` has a ``--multiple`` argument to record multiple devices at
335 …$ sudo libinput record --multiple --output-file=touchpad-bug.yml /dev/input/event17 /dev/input/eve…
344      $ sudo libinput replay touchpad-bug.yml
349 Measuring device properties with libinput measure
352 The ``libinput measure`` tool is a multiplexer for various sub-tools that can
355 Please see the **libinput-measure(1)** man page for information about what
361 Analyzing device events with libinput analyze
364 The ``libinput analyze`` tool is a multiplexer for various sub-tools that
367 Please see the **libinput-analyze(1)** man page for information about what
377 The ``libinput quirks`` tool can show quirks applied for any given device. ::
379      $ libinput quirks list /dev/input/event0