1
0

libinput-debug-gui.man 4.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112
  1. .TH libinput-debug-gui "1" "" "libinput @LIBINPUT_VERSION@" "libinput Manual"
  2. .SH NAME
  3. libinput\-debug\-gui \- visual debug helper for libinput
  4. .SH SYNOPSIS
  5. .B libinput debug\-gui \fI[options]\fB
  6. .PP
  7. .B libinput debug\-gui \fI[options]\fB \-\-udev \fI<seat>\fB
  8. .PP
  9. .B libinput debug\-gui \fI[options]\fB [\-\-device] \fI/dev/input/event0\fB
  10. .SH DESCRIPTION
  11. .PP
  12. The
  13. .B "libinput debug\-gui"
  14. tool creates a libinput context and a full-screen GTK window to visualize
  15. events processed by libinput. This tool exclusively grabs pointing devices
  16. and stops them from interacting with the rest of the GUI.
  17. .PP
  18. .B Hit Esc to exit this tool.
  19. .PP
  20. This is a debugging tool only, its output or behavior may change at any
  21. time. Do not rely on the output or the behavior.
  22. .PP
  23. This tool usually needs to be run as root to have access to the
  24. /dev/input/eventX nodes.
  25. .SH OPTIONS
  26. .TP 8
  27. .B \-\-device \fI/dev/input/event0\fR
  28. Use the given device with the path backend. The \fB\-\-device\fR argument may be
  29. omitted.
  30. .TP 8
  31. .B \-\-grab
  32. Exclusively grab all opened devices. This will prevent events from being
  33. delivered to the host system.
  34. .TP 8
  35. .B \-\-help
  36. Print help
  37. .TP 8
  38. .B \-\-udev \fI<seat>\fR
  39. Use the udev backend to listen for device notifications on the given seat.
  40. The default behavior is equivalent to \-\-udev "seat0".
  41. .TP 8
  42. .B \-\-verbose
  43. Use verbose output
  44. .PP
  45. For libinput configuration options, see libinput-debug-events(1)
  46. .SH FEATURES
  47. .PP
  48. .TP 8
  49. .B Cursor movement
  50. The cursor is displayed as black triangle. Various markers are displayed in
  51. light grey to help debug cusor positioning. The cursor movement is
  52. the one as seen by libinput and may not match the cursor movement of the
  53. display server.
  54. .PP
  55. The unaccelerated cursor motion is displayed as a grey upside-down triangle.
  56. The movement of this cursor typically reflects the relative motion in device
  57. units and can differ significantly to the normal cursor movement.
  58. .PP
  59. The unaccelerated cursor motion is also displayed as a yellow snake. This is
  60. the connected set of recent deltas. Unlike the unaccelerated cursor, these
  61. coordinates are not clipped to the window.
  62. .TP 8
  63. .B Button testing
  64. Four oblongs are displayed at the bottom. The top three are left, middle,
  65. right, the bottom one is for any other button and displays the button name
  66. on press.
  67. .TP 8
  68. .B Scrolling
  69. The green oblongs show the scrolling in continuous space, the smaller red
  70. oblongs the scroll steps in discrete steps.
  71. .TP 8
  72. .B Gestures
  73. A set of four horizontal black rings show swipe gestures, with the number of
  74. detected fingers filled in. A set of two black rings show pinch gestures,
  75. filled when events are detected.
  76. .TP 8
  77. .B Touch and absolute mouse events
  78. Touch and absolute mouse events are displayed as red and blue circles,
  79. respectively, at the touch point or absolute position.
  80. .TP 8
  81. .B Tablet tools
  82. Events from tablet tools show a cyan square at the proximity-in and
  83. proximity-out positions. The tool position is shown as circle and increases
  84. in radius with increasing pressure or distance. Pressure and distance are
  85. also shown in the vertical bar south-east of center. Where tilt is
  86. available, the circle changes to an ellipsis to indicate the tilt angle.
  87. Relative events from the tablet tool are displayed as a yellow snake, always
  88. starting from the center of the window on proximity in. Button events are
  89. displayed in the bottom-most button oblong, with the name of the button
  90. displayed on press.
  91. .TP 8
  92. .B Tablet pads
  93. Button events are displayed in the bottom-most button oblong, with the name
  94. of the button displayed on press. Dials, ring and strip events are displayed in
  95. the yellow 'IO' symbol, with the position of the ring or strip or the
  96. delta of the dial filled in when events are available. The number of the dial,
  97. ring or strip is displayed when an event is available.
  98. .TP 8
  99. .B Kernel events
  100. Left of the center is a blue ring to debug kernel relative events (REL_X and
  101. REL_Y). Each unit is displayed as one arrow in the respective direction.
  102. Right of the center is a blue oblong representing the most recently-used
  103. touch device. Touch events are displayed as they are read from the kernel.
  104. .SH NOTES
  105. .PP
  106. Events shown by this tool may not correspond to the events seen by a
  107. different user of libinput. This tool initializes a separate context.
  108. .SH LIBINPUT
  109. Part of the
  110. .B libinput(1)
  111. suite