summaryrefslogtreecommitdiff
path: root/evtest.txt
blob: 685a4de58e6eb64c687af40256e28634a4df0484 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
EVTEST(1)
=========

NAME
----

     evtest - Input device event monitor

SYNOPSIS
--------
     evtest "/dev/input/eventX"

DESCRIPTION
-----------
evtest displays information on the input device specified on the command
line, including all the events supported by the device. It then monitors the
device and displays all the events layer events generated.

evtest needs to be able to read from the device; in most cases this means it
must be run as root.

evtest is commonly used to debug issues with input devices in X.Org. The
output of evtest shows the information presented by the kernel; based on
this information it can be determined whether a bug may be a kernel or an
X.Org issue.

DIAGNOSTICS
-----------
If evtest does not show any events even though the device is being used, the
device may be grabbed by a process (EVIOCGRAB).  This is usually the case
when debugging a synaptics device from within X. VT switching to a TTY or
shutting down the X server terminates this grab and synaptics devices can be
debugged.

SEE ALSO
--------
inputattach(1)

AUTHOR
------
evtest was written by Vojtech Pavlik <vojtech@suse.cz>.

This manual page was written by Stephen Kitt <steve@sk2.org>, based on that
present in the lineakd package, for the Debian GNU/Linux system (but may be
used by others).