From the libinput wiki page:
- libinput is a library to handle input devices in Wayland compositors and to provide a generic X.Org input driver. It provides device detection, device handling, input device event processing and abstraction to minimize the amount of custom input code compositors need to provide the common set of functionality that users expect.
The X.Org input driver supports most regular input devices. Particularly notable is the project's goal to provide advanced support for touch (multitouch and gesture) features of touchpads and touchscreens. See the libinput documentation for more information.
- For Wayland, the package should be installed as a dependency of any graphical environment you use that has Wayland, and no additional driver is needed.
- For Xorg, is also a dependency. It is "a thin wrapper around libinput and allows for libinput to be used for input devices in X. This driver can be used as as drop-in replacement for evdev and synaptics." . It replaces other packages used for input with X (i.e., those prefixed with
You may want to installto be able to change settings at runtime.
For Wayland, there is no libinput configuration file. The configurable options depend on the progress of your desktop environment's support for them; see #Graphical tools. To configure options that your desktop environment does not yet support (e.g. touchpad scroll speed on GNOME), AUR may be used as a work-around. Available options for that tool are documented in the libinput-config README.
For Xorg, a default configuration file for the wrapper is installed to
/usr/share/X11/xorg.conf.d/40-libinput.conf. No extra configuration is necessary for it to autodetect keyboards, touchpads, trackpointers and supported touchscreens.
# libinput list-devices
It will output the devices on the system and their respective features supported by libinput.
After a restart of the graphical environment, the devices should be managed by libinput with default configuration, if no other drivers are configured to take precedence.
Seefor general options to set and information about allowable values. The xinput tool is used to view or change options available for a particular device at runtime. For example:
$ xinput list
to view all devices and determine their names and numbers. In the following,
device is either the name or number identifying the device to operate with.
$ xinput list-props device
to view and
$ xinput set-prop device option setting
to change a setting.
option can be either the number or the name of the option. For example, to set both options of libinput Click Method Enabled (303), either of the following can be issued:
$ xinput set-prop 14 303 1 1
$ xinput set-prop 14 "libinput Click Method Enabled" 1 1
Via Xorg configuration file
Alternative drivers for Xorg#Input devices can generally be installed in parallel. If you intend to switch driver for a device to use libinput, ensure no legacy configuration files
/etc/X11/xorg.conf.d/ for other drivers take precedence.
- If you have libinput and synaptics installed in parallel with default configuration (i.e. no files in
/etc/X11/xorg.conf.dfor either), synaptics will take precedence due to its higher numeric order
70-in the default installation directory. To avoid this, you can symlink the default libinput configuration (
/etc/X11/xorg.conf.d/where directory search order precedence over
70-synaptics.confwill take place instead:
# ln -s /usr/share/X11/xorg.conf.d/40-libinput.conf /etc/X11/xorg.conf.d/40-libinput.conf
If you do have
/etc/X11/xorg.conf.d/ configuration files for both, the libinput file must be ordered second; see Xorg#Using .conf files. If you want to disable libinput (and fallback to older drivers) - just remove the previously created symbolic link from
- If a configuration file seems to have no effect at all, check that it is readable by unprivileged users.
One way to check which devices are managed by libinput is the xorg logfile. For example, the following:
$ grep -e "Using input driver 'libinput'" /path/to/Xorg.0.log
[ 28.799] (II) Using input driver 'libinput' for 'Power Button' [ 28.847] (II) Using input driver 'libinput' for 'Video Bus' [ 28.853] (II) Using input driver 'libinput' for 'Power Button' [ 28.860] (II) Using input driver 'libinput' for 'Sleep Button' [ 28.872] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard' [ 28.878] (II) Using input driver 'libinput' for 'SynPS/2 Synaptics TouchPad' [ 28.886] (II) Using input driver 'libinput' for 'TPPS/2 IBM TrackPoint' [ 28.895] (II) Using input driver 'libinput' for 'ThinkPad Extra Buttons'
is a notebook without any configuration files in
/etc/X11/xorg.conf.d/, i.e. devices are auto-detected.
Of course you can elect to use an alternative driver for one device and libinput for others. A number of factors may influence which driver to use. For example, in comparison to Touchpad Synaptics the libinput driver has fewer options to customize touchpad behaviour to one's own taste, but far more programmatic logic to process multitouch events (e.g. palm detection as well). Hence, it makes sense to try the alternative, if you are experiencing problems on your hardware with one driver or the other.
Custom configuration files should be placed in
/etc/X11/xorg.conf.d/ and following a widely used naming schema
30-touchpad.conf is often chosen as filename.
/usr/share/X11/xorg.conf.d/40-libinput.conffor guidance and refer to the manual page for a detailed description of available configuration options.
A basic configuration should have the following structure:
Section "InputClass" Identifier "devname" Driver "libinput" ... EndSection
You may define as many sections as you like in a single configuration file (usually one per input device). To configure the device of your choice specify a filter by using one of the available filters from, e.g.
The input device can then be configured with any of the lines of. Common options include:
Option "Tapping" "on": tapping a.k.a. tap-to-click
Option "ClickMethod" "clickfinger": trackpad no longer has middle and right button areas and instead two-finger click is a context click and three-finger click is a middle click, see the docs.
Option "NaturalScrolling" "true": natural (reverse) scrolling
Option "ScrollMethod" "edge": edge (vertical) scrolling
Bear in mind that some of them may only apply to certain devices and you will need to restart X for changes to take effect.
There are different GUI tools:
- Control center has a basic UI. See GNOME#Mouse and touchpad.
- offers some additional settings.
- Similar to the GNOME UI, with more options.
- Mouse option available in the settings panel. Also accessible using
- Mouse option available in the settings panel. Also accessible using
- KDE Plasma 5:
- Keyboard, mouse and controller devices can be configured from System Settings.
- Configured from the Mouse and Touchpad submenu in .
Tips and tricks
Swapping two- and three-finger tap for a touchpad is a straight forward example. Instead of the default three-finger tap for pasting, you can configure two-finger tap pasting by setting the
TappingButtonMap option in your Xorg configuration file. To set 1/2/3-finger taps to left/right/middle, set
lrm, for left/middle/right set it to
Section "InputClass" Identifier "touchpad" Driver "libinput" MatchIsTouchpad "on" Option "Tapping" "on" Option "TappingButtonMap" "lmr" EndSection
Remember to remove
MatchIsTouchpad "on" if your device is not a touchpad and adjust the
For some devices, it is desirable to change the button mapping. A common example is the use of a thumb button instead of the middle button (used in X11 for pasting) on mice where the middle button is part of the mouse wheel. You can query the current button mapping via:
$ xinput get-button-map device
where device is either the device name or the device ID, as returned by
xinput list. You can freely permutate the button numbers and write them back. Example:
$ xinput set-button-map device 1 6 3 4 5 0 7
In this example, we mapped button 6 to be the middle button and disabled the original middle button by assigning it to button 0. For more information, please read about "ButtonMapping" section in Wayland, but be aware both the device number and its button-map will be different. Hence, settings are not directly interchangeable.. This may also be used for
Some devices occur several times under the same device name, with a different amount of buttons exposed. The following is an example for reliably changing the button mapping for a Logitech Revolution MX mouse via xinitrc:
... for i in $(xinput list | grep "Logitech USB Receiver" | perl -n -e'/id=(\d+)/ && print "$1\n"') do if xinput get-button-map "$i" 2>/dev/null| grep -q 20; then xinput set-button-map "$i" 1 17 3 4 5 8 7 6 9 10 11 12 13 14 15 16 2 18 19 20 fi done ...
You could also use the Xorg configure file to do that. The trackball used in this example has a physical scroll wheel, for those devices without that may need to refer the configure for Logitech Marble Mouse. The physical buttons in Kensington Slimblade Trackball layout are:
----------- |2(M)|8(S)| ----------- |1(L)|3(R)| -----------
So for the left hand user, you may use the configure below, although you do not have neither a scroll up button nor scroll down button, you cannot disable them in configure or some application will not response to the action of the wheel.
----------- |2(N)|8(M)| ----------- |1(R)|3(L)| -----------
Section "InputClass" Identifier "Trackball" MatchProduct "Kensington Kensington Slimblade Trackball" MatchProduct "Trackball" Driver "libinput" Option "ButtonMapping" "3 0 1 4 5 6 7 8 2" EndSection
Change touchpad sensitivity
The method of finding the correct thresholds for when libinput registers a touch as DOWN and back UP again can be found  in the upstream documentation.
Custom touchpad pressure values can be set via temporary local device quirks. See .
To disable the touchpad, first get its name with
xinput list and then disable it with
xinput disable name.
- It is more robust to disable it by name than by ID number. The devices may be renumbered.
- It will be necessary to quote the name if it contains spaces.
To make it permanent, see Autostarting.
To toggle, write a script such as .
While the libinput driver already contains logic to process advanced multitouch events like swipe and pinch gestures, the Desktop environment or Window manager might not have implemented actions for all of them yet.
For EWMH (see also wm-spec) compliant window managers, the libinput-gestures utility can be used meanwhile. The program reads libinput gestures (through
libinput debug-events) from the touchpad and maps them to gestures according to a configuration file. Hence, it offers some flexibility within the boundaries of libinput's built-in recognition.
To use it, install the README for details.AUR package. You can use the default system-wide configured swipe and pinch gestures or define your own in a personal configuration file, see the
fusuma Ruby gem:
$ gem install fusuma
Alternatively, there is alsoAUR.
fusuma-plugin-sendkeyRuby gem supports both X and Wayland
~/.config/fusuma/config.yml you have to set something like:
swipe: 3: left: sendkey: 'LEFTALT+RIGHT' right: sendkey: 'LEFTALT+LEFT' up: sendkey: 'LEFTALT+LEFTSHIFT+TAB' down: sendkey: 'LEFTALT+TAB' pinch: in: sendkey: 'LEFTALT+LEFTSHIFT+TAB' out: sendkey: 'LEFTALT+TAB' threshold: swipe: 0.5 pinch: 0.2 interval: swipe: 0.2 pinch: 0.2
swipe: 3: left: command: 'xdotool key alt+Right' right: command: 'xdotool key alt+Left' up: command: 'xdotool key ctrl+shift+plus' down: command: 'xdotool key ctrl+minus' pinch: in: command: 'xdotool key ctrl+shift+plus' out: command: 'xdotool key ctrl+minus' threshold: swipe: 0.5 pinch: 0.2 interval: swipe: 0.2 pinch: 0.2
Same thing for
The swipe threshold is important for not swiping back too many pages.
Notice that the configure is for three fingers swipe. Two fingers swipe is not supported .
Gebaar is another gesture recognizer. Unlike Fusuma, it does not support pinching (support is planned in the future though) and thresholds, but in addition to swiping left, right, up and down with 3/4 fingers, it also supports diagonal swipes, which Fusuma does not.
There is a fork of gebaar at Gebaar which could be installed through AUR which supports pinch gestures and adds additional features to original gebaar. Take in mind that this version is currently under active development and introduces configuration changes which makes it incompatable to original Gebaar
For deeper integration with GNOME, there is GnomeExtendedGestures ( AUR). Three finger horizontal and vertical gestures can be configured to perform gnome-shell actions (such as toggling the application overview or cycling between them).
There is a nice trick to optimize scrolling with a mouse or trackball by holding a mouse button (like right or middle button, or some other if the mouse has more buttons) and moving the mouse. Very useful in case your mouse does not have the mouse wheel (often the case with the trackballs). To do that one has to set
button and specify the mouse button in the
ScrollButton option for the action. Here is an example for configuration to achieve that:
Section "InputClass" Identifier "system-mouse" MatchIsPointer "on" Option "ScrollMethod" "button" Option "ScrollButton" "3" EndSection
Mouse wheel scrolling speed scaling
For some mouses, especially when using on a HiDPI desktop, the wheel scrolls too slow. A patch is submitted to libinput but it has not been accepted. There is a third-party xf86-input-libinput that incoperates this patch.
This patch introduces a new property
libinput Scroll Distance Scale to mouses, and you can set a scaling factor like
$ xinput --set-prop 'RAPOO Rapoo 2.4G Wireless Device' 'libinput Scroll Distance Scale' 2.5 2.5
RAPOO Rapoo 2.4G Wireless Device is the name of your mouse device, listed in
2.5 2.5 are the scaling factors, for x- and y-axis, respectively.
Alternatively, install Xorg, then enlarge y-axis scroll distance to 6 times byAUR and restart
$ echo 6 > /tmp/libinput_discrete_deltay_multiplier
Here is an example to modify the scaling factor upon focusing change
First, see whether executing
libinput debug-events can support you in debugging the problem, see for options.
Some inputs require kernel support. The tool evemu-describe from thepackage can be used to check:
Compare the output of software supported input trackpad driver with a supported trackpad. i.e. a couple of ABS_ axes, a couple of ABS_MT axes and no REL_X/Y axis. For a clickpad the
INPUT_PROP_BUTTONPAD property should also be set, if it is supported.
Touchpad not working in GNOME
Ensure the touchpad events are being sent to the GNOME desktop by running the following command:
$ gsettings set org.gnome.desktop.peripherals.touchpad send-events enabled
Additionally, GNOME may override certain behaviors, like turning off Tapping and forcing Natural Scrolling. In this case the settings must be adapted using GNOMEs
gsettings command line tool or a graphical frontend of your choice. For example if you wish to enable Tapping and disable Natural Scrolling for your user, adjust the touchpad key-values like the following:
$ gsettings set org.gnome.desktop.peripherals.touchpad tap-to-click true $ gsettings set org.gnome.desktop.peripherals.touchpad natural-scroll false
Inertial scrolling does not work in KDE
- libinput Wayland documentation
- FOSDEM 2015 - libinput - Hans de Goede on goals and plans of the project
- Peter Hutterer's Blog - numerous posts on libinput from one of the project's hackers
- Talk by the primary libinput maintainer outlining the history and state (as of 2020) of Linux input device handling
- Blog post by the libinput maintainer outlining the rationale for libinput