X11Libre/xserver
Xserver
This project is an X11 window system server that coordinates graphical output and input devices. It functions as a display server, a hardware driver manager for graphics and input modules, and a graphics server capable of rendering directly to a generic framebuffer.
The server provides multi-seat display management to isolate input and display devices for different concurrent users. It also implements namespace isolation to separate clients and restrict resource access, preventing interference between different user sessions or processes.
The system manages GPU driver integration through dynamic module loading, including the ability to override version checks for proprietary drivers. It handles display mode control via atomic mode setting to prevent visual tearing and utilizes a client-server network protocol to decouple the server from applications. Other capabilities include shared memory buffer exchange for pixel data and hardware seat abstraction.
Features
- X11 Server Sharing - Functions as an X11 window system server that coordinates graphical output and input devices for desktop environments.
- X11 Display Server Management - Runs an X11 window system server that coordinates graphical output and input devices for desktop environments and applications.
- GPU Driver Modules - Loads GPU driver modules dynamically at runtime, with version override support for proprietary drivers.
- Display Output Drivers - Drives display output with TearFree and atomic modesetting for smooth, tear-free rendering.
- Framebuffer Renderers - Renders graphical output directly to a generic framebuffer on systems without dedicated GPU drivers.
- Framebuffer Display Servers - Ships a generic framebuffer X server that renders directly to a framebuffer on systems without dedicated GPU drivers.
- Display Server Protocols - Ships a network protocol that decouples client applications from the display server for resource exchange.
- Atomic Mode Setting - Implements atomic mode setting to synchronize display configuration updates and prevent visual tearing.
- TearFree Rendering Servers - Provides a graphics server with atomic mode setting and TearFree rendering for tear-free display output.
- Multi-Seat Display Servers - Manages multiple independent user sessions with isolated input and display devices as a multi-seat display server.
- Dynamic GPU Driver Loading - Loads and manages GPU driver modules dynamically, including version override support for proprietary drivers.
- Hardware Seat Abstraction - Abstracts input and display devices into logical seats for multi-user concurrent access via seatd or systemd-logind.
- Hardware Seat Management - Supports seat management via seatd or systemd-logind to handle multiple independent user sessions.
- X Client Namespace Isolation - Enforces namespace-based isolation for X clients, preventing cross-application interference via private selections and authentication tokens.
- X Client Namespace Isolations - Implements namespace isolation for X clients with private selections and no cross-namespace resource access.
- Display Tear-Free Rendering - Configures atomic mode setting and TearFree rendering to eliminate visual tearing on display outputs.
- Shared Memory Buffers - Transfers pixel data between clients and server using shared memory buffers for efficient graphical updates.
- Window Managers - Runs window managers such as i3, dwm, and Openbox on top of the display server.
- Linux Desktop Environments - Runs desktop environments such as GNOME, KDE, and Xfce on top of the display server.
- Auth Token Namespace Mappings - Maps each X client to a namespace based on the authentication token it presents for per-token isolation.
- X Client Isolations - Separates X clients using the Xnamespace extension to prevent interference between applications.
- Session Display Managers - Supports display managers such as GDM, LightDM, and SDDM to start and manage X11 sessions.
Star history
How this analysis was created: This summary and feature list were written by an AI model that read the project's README and public documentation pages. Each feature links to the documentation it came from; stars, license and language come straight from the GitHub API. The model does not read the source code, and the analysis is refreshed when the project is re-analysed. Learn more on our About page.
