Michael Conrad
and 1 contributors


X11::Xlib - Low-level access to the X11 library


  # C-style
  use X11::Xlib ':all';
  my $display = XOpenDisplay($conn_string);
  XTestFakeMotionEvent($display, undef, 50, 50);
  # or, Object-Oriented perl style:
  use X11::Xlib;
  my $display= X11::Xlib->new($conn_string);  # shortcut for X11::Xlib::Display->new
  $display->fake_motion(undef, 50, 50)

  # Remap Caps_Lock to a Smiley face
  use X11::Xlib;
  my $display= X11::Xlib->new;
  my $caps_code= $display->keymap->find_keycode('Caps_lock') // 0x42;
  $display->keymap->modmap_del_codes(lock => $caps_code);
  $display->keymap->keymap->[$caps_code]= [("U263A") x 4];


This module provides low-level access to Xlib functions.

This includes access to some X11 extensions like the X11 test library (Xtst).

If you import the Xlib functions directly, or call them as methods on an instance of X11::Xlib, you get a near-C experience where you are required to manage the lifespan of resources, XIDs are integers instead of objects, and the library doesn't make any attempt to keep you from passing bad data to Xlib.

If you instead create a X11::Xlib::Display object and call all your methods on that, you get a more friendly wrapper around Xlib that helps you manage resource lifespan, wraps XIDs with perl objects, and does some sanity checking on the state of the library when you call methods.


The X11::Xlib connection is a hashref with a few attributes and methods independent of Xlib.


Boolean flag that determines whether the destructor will call "XCloseDisplay". Defaults to true for connections returned by "XOpenDisplay".


  # Global error handler
  # Per-connection error handler
  my $display= X11::Xlib->new;
  sub my_callback {
    my ($display, $event)= @_;

By default, Xlib aborts the program on a fatal error. Use this method to install an error-handling callback to gracefully catch and deal with errors. On non-fatal errors, $event will be the error event from the server. On fatal errors, $event will be undef. You can also install a handler on an individual connection. On a nonfatal error, both the connection and global error handlers are invoked. On a fatal error, all error handlers are invoked.

Setting a value for this attribute automatically installs the Xlib error handler, which isn't enabled by default.

Note that this callback is called from XS context, so your exceptions will not travel up the stack. Also note that on Xlib fatal errors, you cannot call any more Xlib functions on the current connection, or on any connection at all once the callback returns.

Be sure to read notes under "ERROR HANDLING"



This is an alias for X11::Xlib::Display->new, to help encourage using the object oriented interface.


Most functions can be called as methods on the Xlib connection object, since this is usually the first argument. Every Xlib function listed below can be exported, and you can grab them all with

  use X11::Xlib ':functions';



  my $display= X11::Xlib::XOpenDisplay($connection_string);

Instantiate a new (C-level) "Display" instance. This object contains the connection to the X11 display. This will be an instance of X11::Xlib. The X11::Xlib::Display object constructor is recommended instead.

The $connection_string variable specifies the display string to open. ("host:display.screen", or often ":0" to connect to the only screen of the only display on localhost) If unset, Xlib uses the $DISPLAY environement variable.

If the handle goes out of scope, its destructor calls XCloseDisplay, unless you already called XCloseDisplay or the X connection was lost. (Be sure to read the notes on "ERROR HANDLING")


  # or, just:
  undef $display

Close a handle returned by XOpenDisplay. You do not need to call this method since the handle's destructor does it for you, unless you want to forcibly stop communicating with X and can't track down your references. Once closed, all further Xlib calls on the handle will die with an exception.


  my $fh= IO::Handle->new_from_fd( $display->ConnectionNumber, 'w+' );

Return the file descriptor (integer) of the socket connected to the server. This is useful for select/poll designs. (See also: "wait_event" in X11::Xlib::Display)


  XSetCloseDownMode($display, $close_mode)

Determines what resources are freed upon disconnect. See X11 documentation.


Most of these functions return an "XEvent" by way of an "out" parameter that gets overwritten during the call, in the style of C. The variable receiving the event does not need to be initialized.


  XNextEvent($display, my $event_return)
  ... # event scalar is populated with event

You probably don't want this. It blocks forever until an event arrives, even ignoring signals. I added it for completeness. See "wait_event" in X11::Xlib::Display for a more perl-ish interface.





  if ( XCheckMaskEvent($display, $event_mask, my $event_return) ) ...
  if ( XCheckTypedEvent($display, $event_type, my $event_return) ) ...
  if ( XCheckWindowEvent($display, $event_mask, $window, my $event_return) ) ...
  if ( XCheckTypedWindowEvent($display, $event_type, $window, my $event_return) ) ...

Each of these variations checks whether there is a matching event received from the server and not yet extracted form the message queue. If so, it stores the event into $event_return and returns true. Else it returns false without blocking.

(Xlib also has another variant that uses a callback to choose which message to extract, but I didn't implement that because it seemed like a pain and probably nobody would use it.)


  XSendEvent($display, $window, $propagate, $event_mask, $xevent)
    or die "Xlib hates us";

Send an XEvent to the server, to be redispatched however appropriate.


  XPutBackEvent($display, $xevent)

Push an XEvent back onto your own incoming queue. This can presumably put arbitrarily bogus events onto your own queue since it returns void.



Push any queued messages to the X11 server. Some Xlib calls perform an implied flush of the queue, while others don't. If you're wondering why nothing happened when you called an XTest function, this is why.


  XSync($display, $discard);

Force a round trip to the server to process all pending messages and receive the responses (or errors). A true value for the second argument will wipe your incoming event queue.


  XSelectInput($display, $window, $event_mask)

Change the event mask for a window.


Xlib provides opaque "Display" and "Screen" structs which have locally- stored attributes, but which you must use method calls to access. For each attribute of a screen, there are four separate ways to access it:

  DisplayFoo($display, $screen_num);     # C Macro like ->{screens}[$screen_num]{foo}
  XDisplayFoo($display, $screen_num);    # External linked function from Xlib
  FooOfScreen($screen_pointer);          # C Macro like ->{foo}
  XFooOfScreen($screen_pointer);         # External linked function from Xlib

Since screen pointers become invalid when the Display is closed, I decided not to expose them, and since DisplayFoo and XDisplayFoo are identical I decided to only implement the first since it makes one less symbol to link from Xlib.

So, if you grab some sample code from somewhere and wonder where those functions went, drop the leading X and do a quick search on this page.


  my $n= ScreenCount($display);

Return number of configured "Screen"s of this display.



  my $w= DisplayWidth($display, $screen);
  my $h= DisplayHeight($display, $screen);
  # use instead of WidthOfScreen, HeightOfScreen

Return the width or height of screen number $screen. You can omit the $screen paramter to use the default screen of your Display connection.



  my $w= DisplayWidthMM($display, $screen);
  my $h= DisplayHeightMM($display, $screen);
  # use instead of WidthMMOfScreen, HeightMMOfScreen

Return the physical width or height (in millimeters) of screen number $screen. You can omit the screen number to use the default screen of the display.


  my $xid= RootWindow($display, $screen)

Return the XID of the X11 root window. $screen is optional, and defaults to the default screen of your connection. If you want a Window object, call this method on X11::Xlib::Display.


  my $visual= DefaultVisual($display, $screen);
  # use instead of DefaultVisualOfScreen

Screen is optional and defaults to the default screen of your connection. This returns a "Visual", not a "XVisualInfo".


  my $bits_per_pixel= DefaultDepth($display, $screen);
  # use instead of DefaultDepthOfScreen, DisplayPlanes, PlanesOfScreen

Return bits-per-pixel of the root window of a screen. If you omit $screen it uses the default screen.



  XMatchVisualInfo($display, $screen, $depth, $class, my $xvisualinfo_return)
    or die "Don't have one of those";

Loads the details of a "Visual" into the final argument, which must be an "XVisualInfo" (or undefined, to create one)

Returns true if it found a matching visual.


  my @info_structs= XGetVisualInfo($display, $mask, $xvis_template);

Returns a list of "XVisualInfo" each describing an available "Visual" which matches the template you provided. (which is also an XVisualInfo)

$mask can be any combination of:


each describing a field of X11::Xlib::XVisualInfo which is relevant to your search.


  my $vis_id= XVisualIDFromVisual($visual);
  # or, assuming $visual is blessed,
  my $vis_id= $visual->id;

Pull the visual ID out of the opaque object $visual.

If what you wanted was actually the "XVisualInfo" for a $visual, then try:

  my ($vis_info)= GetVisualInfo($display, VisualIDMask, { visualid => $vis_id });
  # or with Display object:


  my $xid= XCreateColormap($display, $rootwindow, $visual, $alloc_flag);
  # or 99% of the time
  my $xid= XCreateColormap($display, RootWindow($display), DefaultVisual($display), AllocNone);
  # and thus these are the defaults
  my $xid= XCreateColormap($display);

Create a "Colormap". The $visual is a "Visual" object, and the $alloc_flag is either AllocNone or AllocAll.


  XFreeColormap($display, $colormap);

Delete a "Colormap", and set the colormap to None for any window that was using it.

Colormap TODO

  XInstallColormap XUninstallColormap, XListInstalledColormaps
  XGetWMColormapWindows XSetWMColormapWindows, XSetWindowColormap
  XAllocColor XStoreColors XFreeColors XAllocColorPlanes XAllocNamedColor
  XQueryColors XCopyColormapAndFree

If anyone actually needs palette graphics anymore, send me a patch :-)



  my $xid= XCreatePixmap($display, $drawable, $width, $height, $depth);

The $drawable parameter is just used to determine the screen. You probably want to pass either DefaultRootWindow($display) or the window you're creating the pixmap for.


  XFreePixmap($display, $pixmap);


  my $pixmap_xid= XCreateBitmapFromData($display, $drawable, $data, $width, $height);

First, be aware that in X11, a "bitmap" is literally a "Bit" "Map" (1 bit per pixel).

The $drawable determines which screen the pixmap is created for. The $data is a string of bytes.

The $data should technically be opaque, written by another X11 function after having rendering graphics to a pixmap or something, but since those aren't implemented here yet, you'll just have to know the format.


  my $pixmap_xid= XCreatePixmapFromBitmapData($display, $drawable, $data,
    $width, $height, $fg, $bg, $depth);

This function uses a bitmap (1 bit per pixel) and a foreground and background color to build a pixmap of those two colors. It's basically upscaling color from monochrome to $depth.



  my $wnd_xid= XCreateWindow(
    $parent_window,  # such as DefaultRootWindow()
    $x, $y,
    $width, $height,
    $color_depth,    # such as $visual_info->depth or DefaultDepth($display)
    $class,          # InputOutput, InputOnly, or CopyFromParent
    $visual,         # such as $visual_info->visual or DefaultVisual($display)
    $attr_mask,      # indicates which fields of \%attrs are initialized
    \%attrs          # struct XSetWindowAttributes or hashref of its fields

The parameters the probably need more explanation are $visual and %attrs.

$visual is a "Visual". You probably either want to use the default visual of the screen ("DefaultVisual") or look up your own visual using "XGetVisualInfo" or "XMatchVisualInfo" (which is a "VisualInfo", and has an attribute ->visual). In the second case, you should also pass $visual_info->depth as the $depth parameter, and create a matching "Colormap" which you pass via the \%attrs parameter.

Since this function didn't have nearly enough parameters for the imaginations of the Xlib creators, they added the full X11::Xlib::XSetWindowAttributes structure as a final argument. But to save you the trouble of setting all those fields, they added an $attr_mask to indicate which fields you are using.

The window is initially un-mapped (i.e. hidden). See "XMapWindow"


  my $wnd_xid= XCreateSimpleWindow(
    $display, $parent_window,
    $x, $y, $width, $height,
    $border_width, $border_color, $background_color

This function basically creates a "child window", clipped to its parent, with all the same visual configuration.

It is initially unmapped. See "XMapWindow".


  XMapWindow($display, $window);

Ask the X server to show a window. This call is asynchronous and you should call "XFlush" if you want it to appear immediately. The window will only appear if the parent window is also mapped. The server sends back a MapNotify event if the Window event mask allows it, and if a variety of other conditions are met. It's really pretty complicated and you should read the offical docs.


  my ($root, $x, $y, $width, $height, $border_width, $color_depth);
  XGetGeometry($display, $drawable, $root, $x, $y, $width, $height, $border_width, $color_depth)
    or die "XGetGeometry failed";
  # All vars declared above should now be defined

This function loads the geometry of the window into the variables you supply. You may omit the ones you don't care about.


  my ($hints_out, $supplied_fields_out);
  XGetWMNormalHints($display, $window, $hints_out, $supplied_fields_out)
    or warn "Doesn't have WM hints";

If a window has Window Manager Normal Hints defined on it, this function will store them into the $hints_out variable (which will become a X11::Xlib::XSizeHints if it wasn't already). It will also set the bits of $supplied_fields_out to indicate which fields the X11 server knows about. This is different from the bits in $hints_out->flags that indicate which individual fields are defined for this window.


  XSetWMNormalHints($display, $window, $hints);

Set window manager hints for the specified window. $hints is an instance of X11::Xlib::XSizeHints, or a hashref of its fields. Note that the ->flags member of this struct will be initialized for you if you pass a hashref, according to what fields exist in the hashref.


  XUnmapWindow($display, $window);

Hide a window.


  XDestroyWindow($display, $window);

Unmap and destroy a window.


These methods create fake server-wide input events, useful for automated testing. They are available through the XTEST extension.

Don't forget to call "XFlush" after these methods, if you want the events to happen immediately.


  XTestFakeMotionEvent($display, $screen, $x, $y, $EventSendDelay)

Fake a mouse movement to position $x,$y on screen number $screen.

The optional $EventSendDelay parameter specifies the number of milliseconds to wait before sending the event. The default is 10 milliseconds.


  XTestFakeButtonEvent($display, $button, $pressed, $EventSendDelay)

Simulate an action on mouse button number $button. $pressed indicates whether the button should be pressed (true) or released (false).

The optional $EventSendDelay parameter specifies the number of milliseconds ro wait before sending the event. The default is 10 milliseconds.


  XTestFakeKeyEvent($display, $kc, $pressed, $EventSendDelay)

Simulate a event on any key on the keyboard. $kc is the key code (8 to 255), and $pressed indicates if the key was pressed or released.

The optional $EventSendDelay parameter specifies the number of milliseconds to wait before sending the event. The default is 10 milliseconds.


These utility functions help identify and convert KeySym values, and do not depend on a connection to an X server.


  my $ident= XKeysymToString($keysym)

Return the ASCII identifier of the KeySym (as in X11/keysym.h) minus the leading "XK_" prefix, or undef of that fails for some reason.

XKeysymToString is the exact reverse of XStringToKeysym.


  my $keysym= XStringToKeysym($string)

Return the keysym number for the symbolic identifier $string. (as per X11/keysym.h, minus the XK_ prefix)

XStringToKeysym is the reverse of XKeysymToString.


  my $keysym= codepoint_to_keysym(ord($char));

Convert a Unicode codepoint to a KeySym value. This isn't a true Xlib function, but fills a gap in the API since Xlib is pretty weak on unicode handling. Every normal unicode codepoint has a keysym value, but if you pass an invalid codepoint you will get undef.


  my $cp= keysym_to_codepoint($keysym);
  my $char= defined $cp? chr($cp) : undef;

Convert a KeySym to a unicode codepoint. Many KeySyms (like F1, Control, etc) do not have any character associated with them, and will return undef. Again, not actually part of Xlib, but provided here for convenience.


Like "codepoint_to_keysym" example above, but takes a string from which it calls ord() on the first character. Returns undef if the string doesn't have a first character.


Like "keysym_to_codepoint" example above, but returns a string if there is a valid codepoint, and undef otherwise.


  XConvertCase($keysym, $lowercase_out, $uppercase_out);

Return the lowercase and uppercase KeySym values for $keysym.



Return true if $keysym is a function key (F1 .. F35)



Return true if $keysym is on numeric keypad.



Return true is key if... honestly don't know :\



Return true if $keysym is a modifier key (Shift, Alt).



Xlib docs are fun. No mention of what "PF" might be.



True for vendor-private key codes.




Return a list of the key codes currently pressed on the keyboard.


  $bool= XGrabKeyboard($display, $window, $owner_events, $pointer_mode, $keyboard_mode, $timestamp)

Direct foxus to the specified window. See X11 docs.


  XUngrabKeyboard($display, $timestamp)


  XGrabKey($display, $keycode, $modifiers, $window, $owner_events, $pointer_mode, $keyboard_mode)

Register a window to receive any matching key events, optionally hiding them from the normal target window.

$keycode is the keyboard scan code to watch for, or AnyKey. $modifiers is a bit mask combined from ControlMask, LockMask, Mod1Mask, Mod2Mask, Mod3Mask, Mod4Mask, Mod5Mask, ShiftMask, or the special mask AnyModifier which means any or none of the modifiers. $window is the XID or X11::Xlib::Window to direct events toward. $owner_events is a boolean of whether to also let the normal target of the key event receive them. $pointer_mode and $keyboard_mode are either GrabModeSync or GrabModeAsync.


  XUngrabKey($display, $keycode, $modifiers, $window)

Cancel a grab registered by "XGrabKey".


  $bool= XGrabPointer($display, $window, $owner_events, $event_mask,
    $pointer_mode, keyboard_mode, confine_to, cursor, timestamp)


  XUngrabPointer(dpy, timestamp)


  XGrabButton($display, $button, $modifiers, $window, $owner_events,
    $event_mask, $pointer_mode, $keyboard_mode, $confine_to, $cursor)


  XUngrabButton($display, $button, $modifiers, $window)


  XAllowEvents($display, $event_mode, $timestamp)

If grab modes used above are GrabModeSync then further X11 input processing is halted until you call this function. See X11 docs.


  XGetKeyboardMapping($display, $keycode, $count)

Return an array of KeySym numbers corresponding to $count key codes, starting at $keycode.

Each position in the per-key array corresponds to a combination of key modifiers (Shift, Lock, Mode). The X11 server may return a variable number of codes per key, which you can determine by dividing the total number of values returned by this function by the $count.

For a more perl-friendly interface, see "load_keymap". For object-oriented access, see X11::Xlib::Keymap.


  XChangeKeyboardMapping($display, $first_keycode, $keysym_per_keycode, \@keysyms, $num_codes);
  # Best explained with an example...
  # KeySym in 0x20..0x7E map directly from Latin1
  my @keycodes= (
    ord('a'), ord('A'), ord('a'), ord('A'),  # want to assign these KeySym to KeyCode 38
    ord('s'), ord('S'), ord('s'), ord('S'),  # and these to KeyCode 39
  XChangeKeyboardMapping($display, 38, 4, \@keycodes, scalar @keycodes);

Update some/all of the KeySyms attached to one or more KeyCodes. In the example above, only the first 4 KeySyms of each KeyCode will be changed. Specify a larger number of $keysym_per_keycode to overwrite more of them.

For a more perl-friendly interface, see "save_keymap". For object-oriented access, see X11::Xlib::Keymap.


  my $keymap= load_keymap($display, $symbolic, $min_key, $max_key);
  my $keymap= load_keymap($display, $symbolic); # all keys
  my $keymap= load_keymap($display); # all keys, symbolic=2

This is a wrapper around "XGetKeyboardMapping" which returns an arrayref of arrayrefs, and also translates KeySym values into KeySym names or unicode characters. If $symbolic is 0, the elements of the arrays are KeySym numbers. If $symbolic is 1, the elements are the KeySym name (or integers, if a name is not available). If $symbolic is 2, the elements are characters for every KeySym that can be un-ambiguously represented by a character, else KeySym names, else integers.

The minimum KeyCode of an X server is never below 8. If you omit $min_key it defaults to 0, and so the returned array will always have at least 8 undef values at the start. This minor waste allows you to index into the array directly with a KeyCode.


  save_keymap($display, \@keymap, $min_key, $max_key);
  save_keymap($display, \@keymap); # to update all keycodes

This is a wrapper around "XChangeKeyboardMapping" that accepts the same array-of-arrays returned by "load_keymap". The first element of the array is assumed to be $min_key unless the array is longer than $max_key in which case the array is assumed to start at 0 and you are requesting that only elements ($min_key .. $max_key) be sent to the X server.

Each element of the inner array can be an integer KeySym, or a KeySym name recognized by "XStringToKeysym", or a single unicode character. If the KeySym is an integer, it must be at least two integer digits, which all real KeySyms should be (other that NoSymbol which has the value 0, and should be represented by undef) to avoid ambiguity with the characters of the number keys. i.e. "4" means "the KeySym for the character 4" rather than the KeySym value 4.


  my $mapping= XGetModifierMapping($display);

Return an arrayref of 8 arrayrefs, one for each modifier group. The inner arrayrefs can contain a variable number of key codes which belong to the modifier group. See X11::Xlib::Keymap for an explanation.


  XSetModifierMapping($display, \@modifiers);

@modifiers is an array of 8 arrayrefs, each holding the set of key codes that are part of the modifier. This is the same format as returned by XGetModifierMapping.



Given a XMappingEvent, reload the internal Xlib cache for the parts of the keymap or modmap which have changed.

The functions below (using the internal Xlib cache) are an alternative to processing the keymap directly.


  XLookupString($key_event, $text_out, $keycode_out);

Given a XKeyEvent, translate the key code and modifiers vs. the internal Xlib cached keymap/modmap and write the text name of the key into $text_out. This will either be a name of a key, or the character the key normally generates in a Latin-1 environment. If $keycode_out is given, it will be overwritten with the numeric value of the KeySym.

(If you want to do more than Latin-1, see X11::Xlib::Keymap for utilities to manipulate the keymap directly.)


  my $keycode= XKeysymToKeycode($display, $keysym)

Return the key code corresponding to $keysym in the current mapping.


  XBell($display, $percent)

Make the X server emit a sound.


Xlib has a lot of C structs. Most of them do not have much "depth" (i.e. pointers to further nested structs) and so I chose to represent them as simple blessed scalar refs to a byte string. This gives you the ability to pack new values into the struct which might not be known by this module, and keeps the object relatively lightweight. Most also have a pack and unpack method which convert from/to a hashref. Sometimes however these structs do contain a raw pointer value, and so you should take extreme care if you do modify the bytes.

Xlib also has a lot of opaque pointers where they just give you a pointer and some methods to access it without any explanation of its inner fields. I represent these with the matching Perl feature for blessed opaque references, so the only way to interact with the pointer value is through XS code. In each case, when the object goes out of scope, this library calls any appropriate "Free" function.

Finally, there are lots of objects which exist on the server, and Xlib just gives you a number ("XID") to refer to them when making future requests. Windows are the most common example. Since these are simple integers, and can be shared among any program connected to the same display, this module allows a mix of simple scalar values or blessed objects when calling any function that expects an XID. The blessed objects derive from X11::Xlib::XID.

Most supported structures have their own package with further documentation, but here is a quick list:


Represents a connection to an X11 server. Xlib provides an opaque pointer Display* on which you can call methods. These are represented by this package, X11::Xlib. The X11::Xlib::Display package provides a more perl-ish interface and some helper methods to "DWIM".


The Xlib Screen* is not exported by this module, since most methods that use a Screen* have a matching method that uses a Display*. If you are using the object-oriented Display you then get Screen objects for convenience, but they are just a wrapper around the Display and screen number instead of screen pointer.


An opaque pointer describing binary representation of pixels for some mode of the display. There's probably only one in use on the entire display (i.e. RGBA) but Xlib makes you look it up and pass it around to various functions.


A more useful struct describing a Visual. See X11::Xlib::XVisualInfo.


A struct that can hold any sort of message sent to/from the server. The struct is a union of many other structs, which you can read about in X11::Xlib::XEvent.


An XID referencing what used to be a palette for 8-bit graphics but which is now mostly a useless appendage to be passed to "XCreateWindow". When using the object-oriented Display, these are wrapped by X11::Xlib::Colormap.


An XID referencing a rectangular pixel buffer. Has dimensions and color depth and is bound to a "Screen". Can be used for copying images, or tiling. When using the object-oriented Display, these are wrapped by X11::Xlib::Pixmap.


An XID referencing a Window. Used for painting, event/input delivery, and having data tagged to them. Not abused nearly as much as the Win32 API abuses its Window structures. See X11::Xlib::Window for details.


Error handling in Xlib is pretty bad. The first problem is that non-fatal errors are reported asynchronously in an API masquerading as if they were synchronous function calls. This is mildly annoying. This library eases the pain by giving you a nice XEvent object to work with, and the ability to deliver the errors to a callback on your display or window object.

The second much larger problem is that fatal errors (like losing the connection to the server) cause a mandatory termination of the host program. Seriously. The default behavior of Xlib is to print a message and abort, but even if you install the C error handler to try to gracefully recover, when the error handler returns Xlib still kills your program. Under normal circumstances you would have to perform all cleanup with your stack tied up through Xlib, but this library cheats by using croak (longjmp) to escape the callback and let you wrap up your script in a normal manner. However, after a fatal error Xlib's internal state could be damaged, so it is unsafe to make any more Xlib calls. This library tries to help enforce that by invalidating all the connection objects.

If you really need your program to keep running your best bet is to state-dump to shared memory and then exec() a fresh copy of your script and reload the dumped state. Or use XCB instead of Xlib.


Xlib libraries are found on most graphical Unixes, but you might lack the header files needed for this module. Try the following:

Debian (Ubuntu, Mint)

sudo apt-get install libxtst-dev


sudo yum install libXtst-devel



This module provides a higher-level API for X input simulation and testing.


Functions provided by X11/Xlib are mostly included in the Gtk2 binding, but through the GTK API and perl objects.


Pure-perl implementation of the X11 protocol.


This module still only covers a fraction of the Xlib API. Patches are welcome :)


Olivier Thauvin, <nanardon@nanardon.zarb.org>

Michael Conrad, <mike@nrdvana.net>


Copyright (C) 2009-2010 by Olivier Thauvin

Copyright (C) 2017 by Michael Conrad

This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself, either Perl version 5.10.0 or, at your option, any later version of Perl 5 you may have available.