a133334270
This adds support for XTEST in Xwayland using EIS, the emulated input library [1]. To differentiate between X11 clients using XTEST, initiate a EI context for each client and use the actual client name, from its command line. When an X11 client first tries to use XTEST to generate emulated input events, a new connection to libEI is initiated by Xwayland on behalf of the X11 client. During that connection phase, the EI server will not be accepting events until the emulated device is actually created, meaning that any XTEST request from the X11 client will be discarded until the EI server is willing to accept events. To avoid that issue, add an event queue in Xwayland per X11 client that will keep those requests, and dequeue them as soon as the EI server is ready, i.e. once the EI device is added. If the X11 client disconnects from the Xserver before the EI server is ready, or if the connection is closed by the EI server, those events are discarded and the queue cleared from any pending events. For 10 minutes after the client disconnects, keep the internal struct alive. If a client with the same commandline arguments connects again, re-use the same struct. This means we are faster with the events the second time around but it also allows the EIS server to pause individual clients that keep sending intermittent events and disconnect immediately (e.g. it'd be possible to pause xdtotool while an authentication prompt is active). [1] https://gitlab.freedesktop.org/libinput/libei Thanks to Jan Beich <jbeich@FreeBSD.org> for fixing the build on BSD. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Co-authored-by: Olivier Fourdan <ofourdan@redhat.com> Co-authored-by: David Redondo <kde@david-redondo.de> Signed-off-by: Olivier Fourdan <ofourdan@redhat.com> |
||
|---|---|---|
| .gitlab-ci | ||
| Xext | ||
| Xi | ||
| composite | ||
| config | ||
| damageext | ||
| dbe | ||
| dix | ||
| doc | ||
| dri3 | ||
| exa | ||
| fb | ||
| glamor | ||
| glx | ||
| hw | ||
| include | ||
| m4 | ||
| man | ||
| mi | ||
| miext | ||
| os | ||
| present | ||
| pseudoramiX | ||
| randr | ||
| record | ||
| render | ||
| test | ||
| xfixes | ||
| xkb | ||
| .appveyor.yml | ||
| .dir-locals.el | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mailmap | ||
| .travis.yml | ||
| COPYING | ||
| README.md | ||
| meson.build | ||
| meson_options.txt | ||
| xorg-server.m4 | ||
| xorg-server.pc.in | ||
| xserver.ent.in | ||
X Server
The X server accepts requests from client applications to create windows, which are (normally rectangular) "virtual screens" that the client program can draw into.
Windows are then composed on the actual screen by the X server (or by a separate composite manager) as directed by the window manager, which usually communicates with the user via graphical controls such as buttons and draggable titlebars and borders.
For a comprehensive overview of X Server and X Window System, consult the following article: https://en.wikipedia.org/wiki/X_server
All questions regarding this software should be directed at the Xorg mailing list:
https://lists.freedesktop.org/mailman/listinfo/xorg
The primary development code repository can be found at:
https://gitlab.freedesktop.org/xorg/xserver
For patch submission instructions, see:
https://www.x.org/wiki/Development/Documentation/SubmittingPatches
As with other projects hosted on freedesktop.org, X.Org follows its Code of Conduct, based on the Contributor Covenant. Please conduct yourself in a respectful and civilized manner when using the above mailing lists, bug trackers, etc: