wayland 1.24 is now available, marking the first major release since version 1.23 and ending more than a year without significant new updates to this fundamental graphics protocol for Linux systems. While this long period without updates might suggest an update full of surprises, the reality is that the official announcement itself has been concise and highlights that the main innovations continue to be developed on the protocols and compositors that work around Wayland rather than at the heart of the software.
Despite the 13 months that have passed since the last version, Wayland 1.24 introduces relevant but discreet technical improvements, ensuring greater maturity and robustness in the ecosystem. Among the most notable new features is the new wl_fixes interface, which allows adding a request to destroy a wl_registry object, thus optimizing resource management on clients.
Improvements and new features included in Wayland 1.24
The focus of Wayland 1.24 has been on refining technical details to facilitate development and use in specific scenarios, such as remote desktops or advanced event management. Some of the most significant changes include:
- wl_keyboard.key repeated state: This feature gives composers the ability to control key repeat, a feature that is especially useful for remote desktop solutions where precise keyboard management is essential.
- Timeouts in event managementWith the introduction of wl_display_dispatch_queue_timeout() and wl_display_dispatch_timeout(), a timeout can now be set when dispatching events, giving you more control over how the GUI responds to certain actions. For more details on recent improvements to Wayland support, see also What's new in SDL for Wayland.
- Access to storage after object destructionThe wl_shm_buffer_ref() and wl_shm_buffer_unref() functions allow access to the underlying storage of wl_shm_buffer even after the protocol object has been disposed. This is useful, for example, when a client terminates execution and associated resources still need to be freed or queried.
A modest but fundamental release for stability
Own communication on the development list has simply listed these changes without going into unnecessary details or announcing major revolutions. This approach highlights that, although the changes are less visible, Wayland 1.24 continues to take small but firm steps towards the consolidation of the protocol, leaving most of the experimentation and evolution in the hands of projects such as the various composers and complementary protocols.
This release reinforces the importance of having a solid and stable foundation for developers and users who depend on a reliable and constantly improving environment, thus solidifying Wayland's position in the Linux ecosystem.
