libinput-analyze(1)

💅 NAME 💅

Okay so bestie, welcome to the libinput-analyze(1) page from the libinput Manual. Here's the whole vibe: libinput-analyze - analyze device data. That's it, that's the mission 💖

✨ SYNOPSIS ✨

libinput analyze [--help] <feature> [<args>]

🦋 DESCRIPTION 🦋

The libinput analyze tool analyzes device data. Depending on what is to be analyzed, this tool may not create a libinput context — lowkey important to know 🫶

This is a debugging tool only, its output may change at any time. Do not rely on the output. 💀

Read that again: debugging tool only, output can change whenever, and you should not rely on it. Fr fr.

This tool may need to be run as root to have access to the /dev/input/eventX nodes. So if those nodes are being gatekeep-y, that's why 👑

🎀 OPTIONS 🎀

• --help — Print help 🫶

🌸 FEATURES 🌸

Features that can be analyzed include:

• libinput-analyze-buttons(1) — analyze the button states of a recording 🎀
• libinput-analyze-per-slot-delta(1) — analyze the delta per event per slot ✨
• libinput-analyze-recording(1) — analyze a recording made with libinput-record(1) 🦋
• libinput-analyze-touch-down-state(1) — analyze the state of each touch in a recording 💅

👑 LIBINPUT 👑

Part of the libinput(1) suite — yes bestie, it's a whole family 💜

---

Signed off with libinput 1.32.0 and the libinput-analyze(1) page, with zero invented dates because the footer didn't hand us one — mwah 🎀😭