libinput-m...d-pressure(1)
π libinput-m...d-pressure(1) π
okay so bestie, welcome to the General Commands Manual page for libinput-measure-touchpad-pressure, which is genuinely one of the cutest little debugging tools in the whole libinput family. grab a snack, we're measuring vibes. π
β¨ NAME β¨
libinput-measure-touchpad-pressure β measure pressure properties of devices
πΈ SYNOPSIS πΈ
libinput measure touchpad-pressure [--help] [options] [/dev/input/event0]
π¦ DESCRIPTION π¦
So the libinput measure touchpad-pressure tool measures the pressure of touches on a touchpad. it's an interactive tool, okay? like, not a "run it and walk away" situation. when you execute it, it will prompt you to interact with your touchpad β yes, that means you, bestie, touching the touchpad with your actual fingers. π
when it terminates, the tool prints a summary of the pressure values it saw. and likeβ¦ this data? it should be attached to any pressure-related bug report. fr fr, do not skip this step, the maintainers need the receipts. πβ¨
if you want the full description of how libinput's pressure-to-click behavior works, go read the online documentation here:
https://wayland.freedesktop.org/libinput/doc/latest/touchpad-pressure.htmlhttps://wayland.freedesktop.org/libinput/doc/latest/palm-detection.html
β οΈ not me having to say this but: this is a debugging tool only. its output may change at any time. do not rely on the output. it's giving chaotic on purpose, periodt. π
also β this tool usually needs to be run as root so it can actually access the /dev/input/eventX nodes. no root, no touchy. π
π OPTIONS π
okay so first thing, the device node situation:
- if a device node is given, this tool opens that device node. straightforward, iconic.
- otherwise, this tool searches for the first node that looks like a touchpad and uses that one. it just picks one, no cap. π
here are your actual options:
--helpβ print help. the classic. your bestie in every situation. π«Ά--touch-thresholds="down:up"β set the logical touch pressure thresholds to down and up, respectively. so here's the tea: when a touch exceeds the pressure in down, it's considered logically down. and if a touch is logically down and then goes below the pressure in up, it's considered logically up. these thresholds have to be in device-specific pressure values, and it is required that down >= up. like, that's not optional, that's the rule. β--palm-threshold=Nβ assume a palm threshold of N. the threshold has to be in device-specific pressure values. πΈ--thumb-threshold=Nβ assume a thumb threshold of N. the threshold has to be in device-specific pressure values. π
and here's the little plot twist: if the touch-thresholds or the palm-threshold are not provided, this tool uses the thresholds provided by the device quirks (if any) or the built-in defaults. so like, it's got your back either way, bestie. π§
π LIBINPUT π
Part of the libinput(1) suite. iykyk. π
and that's the whole page!! mwah π this one lives in the General Commands Manual, and the footer on the original was literally just libinput-m...d-pressure(1) all over again β so hey, consider yourself signed off, you absolute icon. go forth and measure those pressure values, main character. slay β¨
π¦ where this page comes from
- alpine 3.24: libinput-doc 1.31.3-r0 Β· MIT
- arch rolling: libinput-tools 1.32.0-1 Β· MIT
- centos-stream 10: libinput-utils 1.30.1-2.el10 Β· MIT
- fedora 43: libinput-utils 1.29.1-1.fc43 Β· MIT
- fedora 43: libinput-utils 1.30.3-1.fc43 Β· MIT
- fedora 44: libinput-utils 1.31.0-1.fc44 Β· MIT
- fedora 44: libinput-utils 1.31.3-1.fc44 Β· MIT
- nixos 26.05: libinput 1.31.3
- nixpkgs unstable: libinput 1.31.3
- ubuntu resolute: libinput-tools 1.31.1-1 Β· MIT
- ubuntu resolute: libinput-tools 1.31.1-1ubuntu1.2 Β· MIT
- ubuntu stonking: libinput-tools 1.31.3-1ubuntu1 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms