xkbevd

xkbevd [-geometry geometry] [-nolisten tcp] [-nodaemon] [-display host:display.screen]

-geometry geometry
    Specifies the initial size and position of the xkbevd window. This follows the standard X geometry string format (e.g., 800x600+100+100).

-nolisten tcp
    Disables listening for TCP connections. This option is typically used in security-sensitive environments to prevent unauthorized access.

-nodaemon
    Runs xkbevd in the foreground. By default, it forks and runs as a background process. This option is useful for debugging purposes.

-display host:display.screen
    Specifies the X server to connect to. If not specified, xkbevd uses the value of the DISPLAY environment variable.

The xkbevd command is a graphical tool for monitoring X Keyboard Extension (XKB) events. It provides a real-time display of various XKB-related events, such as key presses, key releases, and state changes. It's particularly useful for debugging XKB configurations and understanding how XKB is functioning within an X server environment. xkbevd allows users to visually inspect the keycodes, symbols, groups, and modifiers associated with these events. This makes it a valuable utility for developers working with keyboard layouts and input methods.

By observing the event stream, one can identify issues related to key mappings, modifier assignment, and overall keyboard behavior. It offers insight into the interaction between the X server, XKB, and applications. xkbevd is often used in conjunction with other XKB tools to diagnose and resolve complex keyboard configuration problems.

xkbevd relies on the X Keyboard Extension being properly configured on the X server. If XKB is not enabled or is misconfigured, xkbevd may not function correctly or provide accurate information.

The main xkbevd window displays a stream of XKB events. Each event is represented by a line of text showing pertinent event information. This display is continuously updated as new events are generated.

The output from xkbevd can be verbose, but is essential when troubleshooting XKB. Pay close attention to the keycode, keysym, state, group, and modifiers associated with each event. These parameters define how the key press is interpreted by the X Server.

xkbcomp(1), setxkbmap(1), xev(1)