Wayland Archive

Today just so happens to be the 40th birthday of X, the venerable windowing system that’s on its way out, at least in the Linux world. From the original announcement by Robert W. Scheifler: I’ve spent the last couple weeks writing a window system for the VS100. I stole a fair amount of code from W, surrounded it with an asynchronous rather than a synchronous interface, and called it X. Overall performance appears to be about twice that of W. The code seems fairly solid at this point, although there are still some deficiencies to be fixed up. We at LCS have stopped using W, and are now actively building applications on X. Anyone else using W should seriously consider switching. This is not the ultimate window system, but I believe it is a good starting point for experimentation. Right at the moment there is a CLU (and an Argus) interface to X; a C interface is in the works. The three existing applications are a text editor (TED), an Argus I/O interface, and a primitive window manager. There is no documentation yet; anyone crazy enough to volunteer? I may get around to it eventually. ↫ Robert W. Scheifler Reading this announcement email made me wonder if way back then, in 1984, the year of my birth, there were also people poo-pooing this new thing called “X” for not having all the features W had. There must’ve people posting angry messages on various BBS servers about how X is dumb and useless since it doesn’t have their feature in W that allows them to use an acoustic modem to send a signal over their internal telephone system by slapping their terminal in just the right spot to activate their Betamax that’s hotwired into the telephone system. I mean, W was only about a year old at the time, so probably not, but there must’ve been a lot of complaining and whining about this newfangled X thing, and now, 40 years later, long after it has outgrown its usefulness, we’re again dealing with people so hell-bent on keeping an outdated system running but hoping – nay, demanding – others to do the actual work of maintaining it. X served its purpose. It took way too long, but we’ve moved on. Virtually every new Linux user since roughly 12-24 months ago will most likely never use X, and never even know what it was. They’re using a more modern, more stable, more performant, more secure, and better maintained system, leading to a better user experience, and that’s something we should all agree on is a good thing.

There’s incredibly good news for people who use accessibility tools on Linux, but who were facing serious, gamebreaking problems when trying to use Wayland. Matt Campbell, of the GNOME accessibility team, has been hard at work on an entirely new accessibility architecture for modern free desktops, and he’s got some impressive results to show for it already. I’ve now implemented enough of the new architecture that Orca is basically usable on Wayland with some real GTK 4 apps, including Nautilus, Text Editor, Podcasts, and the Fractal client for Matrix. Orca keyboard commands and keyboard learn mode work, with either Caps Lock or Insert as the Orca modifier. Mouse review also works more or less. Flat review is also working. The Orca command to left-click the current flat review item works for standard GTK 4 widgets. ↫ Matt Campbell One of the major goals of the project was to enable such accessibility support for Flatpak applications without having to pass an exception for the AT-SPI bus. what this means is that the new accessibility architecture can run as part of a Flatpak application without having to break out of their sandbox, which is obviously a hugely important feature to implement. There’s still a lot of work to be done, though. Something like the GNOME shell doesn’t yet support Newton, of course, so that’s still using the older, much slower AT-SPI bus. Wayland also doesn’t support mouse synthesizing yet, things like font, size, style, and colour aren’t exposed yet, and there’s a many more limitations due to this being such a new project. The project also isn’t trying to be GNOME-specific; Campbell wants to work with the other desktops to eventually end up with an accessibility architecture that is truly cross-desktop. The blog post further goes into great detail about implementation details, current and possible future shortcomings, and a lot more.

Wayland 1.23.0 has been released. This new release includes the usual bugfixes and protocol clarifications, a number of new features few of us will really understand because we lack the expertise, and most importantly of all: OpenBSD support. That’s it. That’s the news.

IceWM, the venerable window manager we’ve all used at some point in our lives, has released a new version, 3.5.0. It’s a relatively minor release, so you’ve got things like a new install option which will install an extra theme, a fix for porting to NetBSD 10, translation updates, and more such small improvements. The AddressBar, a command line in the taskbar that can be summoned with ctrl+alt+space, also got some love, with file argument completion and support for the cd and pwd commands. You can compile IceWM yourself, of course, but it’ll most likely find its way into your distribution’s repository quickly enough.

Ordinary modifiers are normally straightforward, in that they are additional keys that are held down as you type the main key. Control, Shift, and Alt all work this way (by default). However, some modifiers are ‘sticky’, where you tap their key once to turn them on and then tap their key again to turn them off. The obvious example of this is Caps Lock (unless you turn its effects off, remapping its physical key to be, say, another Ctrl key). Another example, one that many X users have historically wound up quietly cursing, is NumLock. Why people wind up cursing NumLock, and why I have a program to control its state, is because of how X programs (such as window managers) often do their key and mouse button bindings. ↫ Chris Siebenmann I always have an applet in my KDE panel that shows me if I have any sticky modifiers enabled without realising it. On some of my keyboards, this isn’t always easily noticable, especially when you’re focused on what’s happening on your display. A little icon that only shows up when a sticky modifier is engaged solves this problem, as it immediately stands out in your peripheral vision.

X Server is slowly being deprecated in the Linux world and being replaced Wayland. Still X11 is an interesting protocol to look at from the perspective of binary communication and management of resource which require fast speeds. In this post I tried to cover basic information and create a simple but working app that is simple, defined in single file and easily compiles. No external code except libc was used. I find it fascinating when you can open black boxes and see how gears move each other. ↫ Hereket As much as the time of X has come and is now finally in the process of going, it’s still an incredibly powerful set of tools that even in a bare state can do way, way more than you think. X has come with its own window manager – twm – for decades, and it includes several basic applications like xedit, xclock, xterm, xeyes. Twm is actually pretty cool, and includes some features, like iconify to desktop, that I wish still existed in modern desktop environments. It’s quite bare-bones, though, and I doubt there’s anyone out there unironically using it today. As the linked article notes, even without advanced, complex libraries, toolkits, desktop environments, and so on, it’s entirely possible to create fully functional windows and applications with X. Of course, this makes perfect sense and shouldn’t be surprising – it’s the X Window System, after all – but you so rarely hear or read about it that you’d almost forget and just assume something like GNOME or KDE is an absolute requirement to use X.

Miracle-wm is a Wayland compositor built atop of Mir, and its core is a tiling window manager like i3 and sway. It intends to offer more features compared to those, though, gunning more for swayfx. The project, led by Canonical’s Matthew Kosarek, recently released version 0.2.0, which comes with a bunch of improvements. It supports sway/i3 IPC now, so that it can function in conjunction with Waybar, a very popular tool in the build-it-yourself Wayland window manager space. There’s also a new feature where individual windows can live on top (Z-axis wise) of the tiling grid, where they work pretty much like regular windows. Another handy addition is that the configuration can be automatically reloaded when you change it. Miracle-wm comes in a snap package, but rpm and deb will arrive in a few days, as well. As the version number suggest, this project is in heavy development.

Every window system has windows, as an entity. Usually we think of these as being used for, well, windows and window like things; application windows, those extremely annoying pop-up modal dialogs that are always interrupting you at the wrong time, even perhaps things like pop-up menus. In its original state, X has more windows than that. Part of how and why it does this is that X allows windows to nest inside each other, in a window tree, which you can still see today with ‘xwininfo -root -tree‘. One of the reasons that X has copious nested windows is that X was designed with a particular model of writing X programs in mind, and that model made everything into a (nested) window. Seriously, everything. In an old fashioned X application, windows are everywhere. Buttons are windows (or several windows if they’re radio buttons or the like), text areas are windows, menu entries are each a window of their own within the window that is the menu, visible containers of things are windows (with more windows nested inside them), and so on. ↫ Chris Siebenmann This is wild.

One of the somewhat odd things about my old fashioned X Window System environment is that when I ‘iconify’ or ‘minimize’ a window, it (mostly) winds up as an actual icon on my root window (what in some environments would be called the desktop), in contrast to the alternate approach where the minimized window is represented in some sort of taskbar. I have strong opinions about where some of these icons should go, and some tools to automatically arrange this for various windows, including the GNU Emacs windows I (now) use for reading email. ↫ Chris Siebenmann Iconification should be possible in any modern desktop environment, and it’s sad that this paradigm has pretty much entirely vanished. I would love for iconified windows to be treated essentially the same way as files, so you can move them around, drop them inside directories, and even move them from one computer to another (assuming they have the application in question installed). If I’m working on a project, and I have a bunch of LibreOffice documents, spreadsheets, browser tabs, notes in a text editor, some images open, and so on, I should be able to iconify them all, keep them in the project’s directory, and de-iconify them as if nothing had ever happened. Right now, you have to use files and application states for that, which is cumbersome and annoying. Sadly, advanced window management is dying. Shame.

While there are a lot of Wayland compositors out there that aren’t too different from each other in terms of features, one of the more unique ones is Greenfield. The Greenfield Wayland compositor has been out there for a few years now as an in-browser HTML5-based solution that is continuing to prove itself capable and even fast enough for handling Linux gaming. ↫ Michael Larabel A rather genius idea for a Wayland compositor.

The Wayland ecosystem had a phenomenal year from much better NVIDIA proprietary driver support, Firefox ending out the year shipping with Wayland support enabled by default, KDE Plasma 6.0 will default to Wayland following many improvements on the KDE side, the Wine Wayland driver upstreamed in its initial form, XWayland continuing to be enhanced, and a lot of other software from desktop environments to apps continuing to embrace Wayland. ↫ Michael Larabel at Phoronix This train ain’t stopping. Dare I say 2024 will be the year of Wayland on the desktop?

We’re hearing more about this recently because the transition is picking up steam. X11’s maintainers have announced an end to its maintenance. Plasma is going Wayland by default, following GNOME. Fedora is dropping X11 support entirely. We’re in the part of the transition where people who haven’t thought about it at all are starting to do so and realizing that 100% of the pieces needed for their specific use cases aren’t in place yet. This is good! Them being heard is how stuff happens. I wish it had happened sooner, but we are where we are, and there are a lot of recent proposals and work around things like remote control, color management, drawing tablet support, and window positioning. There will probably be an awkward period before all of these pieces are in place for all of the people. And for the those who really do suffer from showstopping omissions, I say keep using X11 until it’s resolved. No one’s stopping you. ↫ Nate Graham at Pointie Stick Will all the people who both can and want to work on X.org please raise their hands? Oh, no hands? What a shame.

While most X.Org Developers Conference talks are around graphics drivers / infrastructure work itself, one of the other interesting XDC 2023 talks was Alexandros Frantzis around the ongoing work of providing a native Wine Wayland driver so that this open-source project can interact directly with Wayland and so Windows games/applications running under Linux will no longer need to go through XWayland. The entire presentation is available on YouTube.

Wayland is all the rage those days. Distributions left and right switch to it, many readers of my previous article on writing a X11 GUI from scratch in x86_64 assembly asked for a follow-up article about Wayland, and I now run Waland on my desktop. So here we go, let’s write a (very simple) GUI program with Wayland, without any libraries, this time in C. In case you’re bored this weekend.