Recientemente a new stable version of the Wayland 1.17 protocol was released, this is a communication mechanism between processes and libraries. Branch 1.17 is backward compatible at the API and ABI level with versions 1.x, but additionally contains a part of the improvements.
AIn addition to troubleshooting and bugs, Wayland 1.17 redesigned the code To display information about internal server errors, it updated the wl_seat protocol and ensured priority use of wl_surface.damage_buffer.
The release of the Weston 6.0 Composite Server, which was expected alongside the release of this version of Wayland 1.17 but was postponed until the end of the week due to the last minute detection of a bug in the meson build scripts.
Weston develops technologies that contribute to full support for the Wayland protocol in desktop environments such as, GNOME, KDE and others.
The goal Weston development is to provide a high-quality code base and working examples for using Wayland in desktop environments and embedded solutions, as platforms for car entertainment systems, smartphones, televisions and other consumer devices.
What's new at Weston?
With the new version of Weston, support for the stable xdg-shell protocol stands out (interface to create and interact with surfaces as with Windows).
Has been added virtual device output support to composer-drm (configured in the remote output section in weston.ini).
Weston receives a new "remoting" plugin to stream output to external hosts using a virtual output device.
The plugin starts automatically with the virtual output settings. The information is transmitted by sending jpeg motion over RTP using gstreamer.
On the remote side, any RTP client is sufficient for display (a remoting-client-receive.bash script based on gstreamer is also prepared).
On the other hand, we find the additional implementation of the simple-dmabuf-egl client with support for sharing multiple video cards using DMABuff technology.
In libweston added API for configuration management (weston_config), for controlling transparency (is_opaque in weston_surface) and synchronization of media based on the sync_file call (zwp_linux_explicit_synchronization_v1).
Of the other support that was added we find:
- Added API for debugging and special debugging mode with verbose log output (weston_debug option).
- The shell was improved for automobile infotainment systems (ivi-shell).
- Added additional input configuration for libinput.
- Improved clipboard support in xwayland.
- Facility provided Weston-screenshooter.
- Gl-renderer adds support for GPU sync via fence sync fd.
wayland 1.17
With this new version of Wayland 1.17 in Firefox 65 support is included for full time work for the environment. To use Wayland, it is now sufficient to launch Firefox with the GDK_BACKEND environment variable set to "wayland".
By your side Fedora 30 has decided to ship a default version of Firefox based on Wayland.
We can also stake among the novelties of this new version that the multimedia center Kodi 18.0 has support for Wayland.
Desktop environments
On the side of desktop environments, We highlight that in MATE 1.22 the desktop panel is adapted to run the back-end based on the Wayland protocol.
En GNOME 3.32 session support was given based on Wayland on a fractional scale.
The first stable version of the Sway 1.0 user environment is available, using Wayland.
In KDE 5.15 XdgStable, XdgPopups and XdgDecoration protocols are fully applied. In Wayland-based environments, virtual desktop support is provided, including the ability to selectively place a window on a given virtual desktop (with X11, this is not possible and the window can be placed on one virtual desktop or all ).
Added support for moving items in drag and drop mode using a gesture on the touch screen or touchpad.
In the beta version of Red Hat Enterprise Linux 8, the GNOME desktop uses Wayland by default.
The Mir display server has stabilized the tools for running Wayland applications and using Mir as a composite server for Wayland.