stable release of the protocol, interprocess communication mechanism and libraries . The 1.18 branch is API and ABI backwards compatible with the 1.x releases, but additionally contains a bunch of improvements. The Weston 8.0 Composite Server, which develops the code base and working examples for using Wayland in desktop environments and embedded solutions, was in the end of January.
Major improvements in Wayland 1.18:
- Added support for the Meson assembly system. The ability to build with autotools has been retained for now, but will be removed in a future release;
- An API for separating proxy objects based on tags, allowing applications and toolkits to share the same Wayland connection;
- Tracked wayland server timers in user space to avoid creating too many file descriptors;
- the wl_global_remove() function, which dispatches the event of removing the global object without clearing it. New Feature eliminate the occurrence of a race condition (race conditions) when deleting global objects. These race conditions could occur because clients were unable to acknowledge receipt of the delete event. The wl_global_remove() function makes it possible to send the removal event first and clear the object only after a certain delay.
Status of Wayland support across applications, desktop environments and distributions:
- Fedora supplying a default build of Firefox based on Wayland. Resolved issues using NVIDIA proprietary binary drivers with Wayland.
experimental ability to automatically start XWayland when trying to run an application based on the X11 protocol.
Added the ability to run X11 applications as root under XWayland in the Wayland environment. SDL for Wayland addresses scaling issues when running older games running at low screen resolutions. The Qt library for use in the GNOME environment is built by default with Wayland support; - Π GNOME is offered as the desktop, with a Wayland-based display server by default;
- In GTK 4 pre-release in GDK implementation of APIs designed with an eye on the use of the Wayland protocol. The GDK backend for Wayland added support for a portal interface for accessing GtkSettings settings, and for working with input methods, support for the text-input-unstable-v3 protocol extension was proposed;
- a project to rid GNOME of bugs and shortcomings that appear when running on top of Wayland;
- In X Wayland GLX handler based on the EGL API, which will eliminate the use of the swrast software rasterizer;
- Among the goals of KDE development for the next two years translating KDE to Wayland. The KDE environment running on top of Wayland is planned to be made primary, and the X11-based environment will be moved to the category of options and optional dependencies. For the reporting period in KDE support for fractional scaling when working on top of Wayland. The Wayland-based KDE session is adapted to work with proprietary NVIDIA drivers. Added the ability to drag & drop application windows using XWayland and Wayland. KWin provides correct mouse wheel scrolling in a Wayland-based environment;
- In GNOME the ability to automate the launch of XWayland when trying to run an application based on the X11 protocol (previously, XWayland had to run constantly);
- work on porting MATE userspace applications to Wayland. IN adapted the Eye of MATE image viewer for Wayland and improved support for Wayland in the MATE panel;
- In Qt Wayland Compositor support for linux-dmabuf-unstable-v1 and wp_viewporter protocols. Added support for fullscreen-shell-unstable-v1 protocol in Qt platform components for Wayland;
- Waypipe - a proxy for the Wayland protocol that allows you to run applications on another host;
- In user environment Significantly improved support for running Wayland;
- For Firefox a new backend for Wayland using the DMABUF mechanism for rendering to textures;
- On Ubuntu in a Wayland-based environment the ability to run X11 applications as root under Xwayland;
- the Wine-wayland patch set and the winewayland.drv driver, which allow Wine to be used in environments based on the Wayland protocol, without the use of XWayland and X11-related components;
- Development of Mir continues as a composite server for Wayland. In the means to ensure the launch of Wayland applications in the Mir environment Wayland protocol extensions. performance optimizations for Wayland-related code, and a new "wayland" graphics platform has been added, allowing Mir to run as a client under another Wayland composite server. experimental support for running X11 applications dynamically in a Wayland-based environment.
- new releases of the Sway custom environment using Wayland;
- Lubuntu distribution moving to Wayland for 2020. Wayland support is planned to be implemented by porting the Openbox window manager to use the Mir display server used as a composite server for Wayland;
- Develops , a Wayland-based composite server for running individual applications in kiosk mode;
- Work continues on the release of the LXQt 1.0.0 user environment, the main task in the development of which is to bring the ability to work on top of Wayland to full readiness;
- Inference system in engine for running Linux virtual machines on ChromeOS built-in support for Wayland clients (virtio-wayland) with the implementation of a composite server on the side of the main host and the ability to effectively use the GPU from guest systems;
- For FreeBSD ports required to build KDE with Wayland support;
- On DragonFly BSD OS port with Wayland and Weston, XWayland support;
- User environments using Wayland ΠΈ merged into a new project . Liri is based on Qt 5 (QML) and promotes Material Design styling;
- Wayland is enabled by default on mobile platforms , , ,