libinput-debug-tablet(1)

✨ libinput-debug-tablet(1) ✨

okay bestie, welcome to the General Commands Manual 💖 this is the page for libinput-debug-tablet, and yes we're gonna read it together, no skimming, i see you 👀

🎀 NAME 🎀

libinput-debug-tablet — debug and visualize tablet axes 🖊️✨

🌸 SYNOPSIS 🌸

libinput debug-tablet [--help] [options] [/dev/input/event0]

that's it, that's the whole vibe check 🫶

🦋 DESCRIPTION 🦋

so the libinput debug-tablet tool is literally just here to debug the values of the various axes on a tablet. interactive queen behavior only 💅 — when you run it, the tool prompts you to go interact with the tablet and then shows you the current value on each available axis. like, you poke the tablet, it tells you the numbers. iconic.

⚠️ this is a debugging tool only, bestie. its output may change at any time. do NOT rely on the output. i'm so serious. do not build your whole thing on top of it, it will betray you 😭

also, ngl, this tool usually needs to be run as root so it can actually get access to the /dev/input/eventX nodes. no root, no nodes, no numbers. them's the rules 👑

💜 OPTIONS 💜

okay so if you hand it a device node, this tool opens that device node. if you don't, it goes searching for the first node that looks like a tablet and just uses that one. it's giving "i'll find one, don't worry" 🧚

• --help — print help. that's the whole thing. it prints help 🫶

and listen — the events shown by this tool may not correspond to the events seen by a different user of libinput. why? because this tool initializes a separate context. so don't come for it when the numbers don't match, it's literally built different 🌈

👑 LIBINPUT 👑

part of the libinput(1) suite 💖 go check the whole family out, iykyk.

and that's a wrap on libinput-debug-tablet(1) 🎀 tysm for reading, bestie, you ate that fr fr ✨ slay 💅🦋🌸