# wayland Published articles for wayland. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Mir/Wayland-Powered Miracle-WM 0.11 Released With New Overview Mode, Window Urgency DevFeed: [Mir/Wayland-Powered Miracle-WM 0.11 Released With New Overview Mode, Window Urgency]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-17T00:58:42Z Content type: release Language: en Sources: [Phoronix]() Topics: [Wayland](), [Library](), [canonical]() Tags: [commands](), [data](), [desktop-linux](), [events](), [github](), [image](), [input](), [ipc](), [library](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [overview](), [phoronix](), [phoronix-test-suite](), [plugins](), [release](), [ubuntu-benchmarks](), [ubuntu-hardware](), [update](), [wayland](), [window](), [windows]() ### AI overview Miracle-WM 0.11, a Wayland compositor built on the Mir library, adds an overview mode, window urgency support, plugin IPC events and commands, and support for newer Mir protocols. The release is built on Mir 2.29. ### Source excerpt Canonical engineer Matthew Kosarek rolled out Miracle-WM 0.11 today as an end-of-summer update to this Wayland compositor built atop the Mir library... ## GNOME 51 Released With Improved Frame Scheduling, Many App Improvements DevFeed: [GNOME 51 Released With Improved Frame Scheduling, Many App Improvements]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-16T16:25:21Z Content type: news Language: en Sources: [Phoronix]() Topics: [releases](), [Wayland](), [Release notes](), [Software](), [ui](), [legacy](), [Nvidia]() Tags: [desktop](), [desktop-linux](), [driver](), [experience](), [faster](), [improvements](), [legacy](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [notes](), [nvidia](), [offline](), [open-source-graphics](), [other](), [phoronix](), [phoronix-test-suite](), [protocols](), [release](), [release-notes](), [settings](), [software](), [time](), [ubuntu](), [ubuntu-benchmarks](), [ubuntu-hardware](), [ui](), [wayland](), [workstation]() ### AI overview GNOME 51 has been released with improved frame scheduling and desktop responsiveness, new Wayland protocol support, removal of legacy NVIDIA EGLStreams driver support, and updates to several GNOME applications and settings. ### Source excerpt Right on schedule and in time for appearing in the likes of Ubuntu 26.10 and Fedora Workstation 45, the GNOME 51 desktop is officially released... ## Maintenance release: Godot 4.7.2 DevFeed: [Maintenance release: Godot 4.7.2]() Original publisher: [Read original article]() Author: Thaddeus Crews Published: 2026-08-18T12:00:00Z Content type: release Language: en Sources: [Godot Engine Official]() Topics: [Godot](), [releases](), [Windows](), [Wayland]() Tags: [backups](), [changelog](), [crash](), [git](), [maintenance](), [release](), [releases](), [wayland](), [windows]() ### AI overview Godot 4.7.2 is the second 4.7 maintenance release. It includes 57 fixes across areas such as the editor, input, networking, rendering, navigation, multiplayer, Wayland, and Windows. ### Source excerpt The second 4.7 maintenance release has arrived! ## Паравиртуализация при отладке графических приложений KasperskyOS в QEMU DevFeed: [Паравиртуализация при отладке графических приложений KasperskyOS в QEMU]() Original publisher: [Read original article]() Author: denis\_molodyakov ("Лаборатория Касперского") Published: 2026-08-11T14:29:29Z Content type: tutorial Language: ru Sources: ["Лаборатория Касперского" RU]() Topics: [qemu](), [ci]() Tags: [ci](), [gpu](), [kasperskyos](), [qemu](), [tag-3bc896470be0](), [tag-9d72402955ce](), [tag-a7f27c878c10](), [tag-c9b6af447c74](), [tag-e5df878d9cd9](), [virtio](), [wayland]() ### AI overview A KasperskyOS graphics team lead describes the challenges of providing distributed developers with access to target hardware for operating-system and driver development. The article introduces their use of paravirtualization with QEMU as a way to address these development and debugging constraints. ### Source excerpt Привет! Меня зовут Денис Молодяков, я -- тимлид команды графики в KasperskyOS. Мы отвечаем за разработку графического стека полного цикла для микроядерной ОС: от создания низкоуровневых графических драйверов до всего необходимого для фреймворков. Современная реальность разработки диктует новые правила: удаленка и распределенные команды стали нормой. Моя команда не исключение -- ребята базируются в разных регионах. При этом каждому разработчику требуется доступ к аппаратным платформам для сборки, запуска ОС, написания и отладки драйверов. Обеспечение каждого сотрудника полным набором плат сопряжено с серьезными логистическими и финансовыми затратами. В этой статье я хочу рассказать, как мы искали оптимальное решение этой проблемы и почему пришли к использованию методики паравиртуализации. Читать далее ## Release candidate: Godot 4.7.2 RC 1 DevFeed: [Release candidate: Godot 4.7.2 RC 1]() Original publisher: [Read original article]() Author: Thaddeus Crews Published: 2026-08-03T12:00:00Z Content type: release Language: en Sources: [Godot Engine Official]() Topics: [Godot](), [releases](), [Windows](), [Wayland]() Tags: [pre-release](), [regression](), [release](), [releases](), [update](), [wayland](), [windows]() ### AI overview Godot announces the Godot 4.7.2 RC 1 maintenance release candidate, following Godot 4.7.1. The release primarily includes regression fixes and other improvements across the editor, core, input, GUI, multiplayer, and platform-specific functionality. ### Source excerpt What happens when you stabilize stability? Let's find out! ## Wayland set the Linux Desktop back by 10 years DevFeed: [Wayland set the Linux Desktop back by 10 years]() Original publisher: [Read original article]() Author: Omar Roth (blog@omar.yt) Published: 2026-03-18T11:40:32Z Content type: opinion Language: en Sources: [Omar Roth]() Topics: [Wayland](), [Linux](), [Post Mortem]() Tags: [developer](), [linux](), [post-mortem](), [wayland]() ### AI overview An opinionated engineering post-mortem argues that Wayland misdirected developer effort and harmed Linux desktop users. It frames the discussion around the limitations of existing systems, why they may not be fixable, and the goals and expected timeline of a new project. ### Source excerpt Wayland has been a broad misdirection and misallocation of time and developer resources at the expense of users. If you're not familiar with this space, hopefully it will still be interesting as an engineering post-mortem on taking on new greenfield projects. Namely: What are the issues with what exists, why can they not be fixed, what do we hope to achieve with a new project, and how long do we expect it to take? ## Supporting Wayland's XDG activation protocol with Gtk/Glib DevFeed: [Supporting Wayland's XDG activation protocol with Gtk/Glib]() Original publisher: [Read original article]() Author: Wladimir Palant Published: 2026-02-03T10:55:20Z Content type: tutorial Language: en Sources: [Almost Secure]() Topics: [Wayland](), [GTK](), [implementation](), [browser]() Tags: [application](), [browser](), [protocol](), [required](), [using](), [wayland]() ### AI overview This tutorial explains how Wayland's XDG activation protocol transfers focus between applications with consent, and documents its implementation in Gtk/Glib. It covers activation tokens, Gio.AppInfo launch contexts, StartupNotify, and manual environment-variable handling. ### Source excerpt One of the biggest sore points with Wayland is its focus stealing protection. The idea is good: an application should not be able to bring itself into focus at an unexpected time, only when the currently active application allows it. Support is still lacking however, which might also be due to Gtk/Glib implementing the required XDG activation protocol but not really documenting it. It took me a bit of time to figure this out without any public information, this article will hopefully make things easier for other people. Contents How the XDG activation protocol works State of implementation in Gtk/Glib Starting applications via Gio.AppInfo Starting applications by other means How the XDG activation protocol works The main idea behind the XDG activation protocol is that focus transfer from one application to another requires consent. With X11 a file manager could just launch the browser for an HTML file and the browser would immediately take focus, even if that browser was already running. With Wayland the file manager has to indicate that the browser is allowed to take focus. It does that by giving the browser its XDG activation token, typically via XDG_ACTIVATION_TOKEN environment variable. The browser can then use that activation token to prove consent and take focus. For this to work the protocol has to be supported on both ends: the file manager must know how to retrieve an activation token and pass it on via XDG_ACTIVATION_TOKEN environment variable, and the browser has to know how to use that token. State of implementation in Gtk/Glib The receiving side has been implemented in Gtk with merge request 7118 and is available starting with Gtk 4.14.6 and 4.15.1. This is the unproblematic part: it is handled automatically and doesn't require the application developer to change anything. The sending side has been implemented in Gtk with merge request 3502 and Glib with merge request 3090, so it is available starting with Gtk 4.10.0 and Glib 2.75.1. This is the part wh ## Using coding agents to redesign the Hyprland screen-share picker DevFeed: [Using coding agents to redesign the Hyprland screen-share picker]() Original publisher: [Read original article]() Author: Sam Saffron Published: 2025-11-23T05:00:51Z Content type: opinion Language: en Sources: [Sam Saffron]() Topics: [Wayland](), [AI-assisted coding](), [Qt](), [ui](), [cursor]() Tags: [blog](), [c-sharp](), [codex](), [coding-agents](), [cursor](), [desktop](), [gemini](), [net](), [rails](), [ruby](), [saffron](), [sam](), [software](), [sql](), [ui](), [wayland](), [weblog](), [work]() ### AI overview The author describes redesigning the Hyprland screen-share picker to address confusing defaults, window selection, and restore-token settings. They used coding agents and multiple language models to prototype and iterate on the interface and its supporting code. ### Source excerpt Over the past few months, I have been struggling with the Hyprland screen-share dialog (hyprland-share-picker via xdg-desktop-portal-hyprland). traditional xdg-desktop-portal-hyprland only title is visible816x483 23.7 KB Under the hood, Chromium / OBS talk to xdg-desktop-portal, which hands off to xdg-desktop-portal-hyprland. That launches hyprland-share-picker (a Qt dialog) which uses the hyprland-toplevel-export-v1 protocol to offer windows and screens. When I am on a call with people I want to quickly share a screen with them, I am confronted with a rather confusing UI: By default it selects the "Screen" tab, which I almost never want On the "Window" tab I get a non-visual list of window names that are hard to decipher There is this whole "restore token" thing that is very confusing. I don't need this checkbox. I accept the risk of always restoring. The "old way" of dealing with this kind of pain was: Open an issue on GitHub which was done back in 2022 Discuss the issue Some brave soul who is familiar with Qt toolkit, various Wayland protocols including the somewhat experimental hyprland-toplevel-export-v1 would take it on herself to implement. Given the complexity of the feature, we would be looking at a week of engineering. So what ends up happening is that we have a bottleneck. Vaxry only has so much time. hyprland is mostly on one person's shoulders, so some little niggles like "my favorite bug" tend to take a back seat for years. However, there is an interesting wind of change as of November 2025. The release of ultra-competent language models such as Gemini 3 Pro, Codex 5.1 Max, and the established Sonnet 4.5 means that when we hit "our favorite bug" we can go ahead and "work something out." Particularly, given the knowledge I had about the problem, the source code of grim hyprland, the protocols involved, and general structure of a solution, I am able to vibe engineer a solution to the problem in an hour or so. I made this new version of the picker using c ## Hired Through GitHub: Part 2 DevFeed: [Hired Through GitHub: Part 2]() Original publisher: [Read original article]() Author: Joseph Lyons Published: 2025-10-30T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [Open Source](), [GitHub](), [pull-requests](), [Linux](), [Wayland]() Tags: [community](), [contributors](), [linux](), [open-source](), [pull-requests](), [wayland]() ### AI overview This article shares Smit Barmase's path from contributing to Zed as an open source project to joining its team. He focused on Linux improvements, fixed bugs, collaborated with Zed staff through reviewed pull requests, and later joined in a community role after Zed sponsored his work. ### Source excerpt More stories from the open source contributors who became core team members. ## How to respond to reactionary behavior in free software communities DevFeed: [How to respond to reactionary behavior in free software communities]() Original publisher: [Read original article]() Author: June Published: 2025-06-30T00:00:00Z Content type: opinion Language: en Sources: [Drew DeVault]() Topics: [Security](), [Wayland](), [Server](), [Software]() Tags: [community](), [security](), [software](), [technical](), [wayland]() ### AI overview The article examines two case studies about responding to reactionary behavior in free software communities. It argues that technical and security-maintenance concerns should be stated directly, while noting the need to keep X usable for desktop environments that will not be ported to Wayland. ### Source excerpt Today, we're looking at two case studies in how to respond when reactionaries appear in your free software community. Exhibit A It is a technical decision. The technical reason is that the security team does not have the bandwidth to provide lifecycle maintenance for multiple X server implementations. Part of the reason for moving X from main to community was to reduce the burden on the security team for long-term maintenance of X. Additionally, nobody so far on the security team has expressed any interest in collaborating with xxxxxx on security concerns. We have a working relationship with Freedesktop already, while we would have to start from the beginning with xxxxxx. Why does nobody on the security team have any interest in collaboration with xxxxxx? Well, speaking for myself only here - when I looked at their official chat linked in their README, I was immediately greeted with alt-right propaganda rather than tactically useful information about xxxxxx development. At least for me, I don't have any interest in filtering through hyperbolic political discussions to find out about CVEs and other relevant data for managing the security lifecycle of X. Without relevant security data products from xxxxxx, as well as a professionally-behaving security contact, it is unlikely for xxxxxx to gain traction in any serious distribution, because X is literally one of the more complex stacks of software for a security team to manage already. At the same time, I sympathize with the need to keep X alive and in good shape, and agree that there hasn't been much movement from freedesktop in maintaining X in the past few years. There are many desktop environments which will never get ported to Wayland and we do need a viable solution to keep those desktop environments working. I know the person who wrote this, and I know that she's a smart cookie, and therefore I know that she probably understood at a glance that the community behind this "project" literally wants to lynch her. In ## Mobian's Early 2025 Developments: Debian Packages, Device Support, and a New Login Screen DevFeed: [Mobian's Early 2025 Developments: Debian Packages, Device Support, and a New Login Screen]() Original publisher: [Read original article]() Author: Mobian team Published: 2025-02-19T00:00:00Z Content type: article Language: en Sources: [Mobian's Blog]() Topics: [Mobile](), [Debian](), [GTK](), [kernels](), [Wayland]() Tags: [adaptive](), [debian](), [kernels](), [mobile](), [patches](), [wayland]() ### AI overview The article reviews recent Mobian developments, including new device support, improved Debian and Mobian packages, plans to reduce the Mobian package repository to mostly Mobian-specific and hardware-support packages, and progress toward a new default mobile login screen. ### Source excerpt Over the past few months, and especially since the last holiday season, many exciting things have happened in Mobian: new devices are (about to be) officially supported, many new and improved packages have made their way into both Debian and Mobian, and we're getting ready for our next stable release! Towards a "device-specific only" repository Thanks to the involvement of upstream developers (by either accepting or writing patches to ensure their applications can be used on mobile devices) and the work of the relevant Debian teams, many GNOME and KDE apps were made adaptive and could be uploaded to the main Debian archive without any additional downstream patch. This allowed us to drop (almost) all of the applications we were distributing through the Mobian package repository: Evince has been replaced with Papers, Loupe is now used instead of EOG and our main camera app is now Snapshot, all available directly from Debian! GNOME Text Editor now works well enough on mobile devices, as do Software and Settings We plan on getting rid of the remaining few ones before the Trixie release: Millipixels (Librem 5 camera app) will be replaced by Megapixels v2 once it hits the Debian archive wake-mobile will likely be dropped as it's no longer maintained, and upstream offers .deb packages for download anyway Except for a patched version of GTK 3 which we will keep maintaining until Phosh is ported to GTK 4, this means all packages in the Mobian archive will be either Mobian-specific (mainly metapackages) or hardware support packages (kernels and device-specific tweaks). A better tomorrow greeter Another major milestone we're about to reach is the move to a new default login screen: back in 2022, we decided that user session management on mobile devices shouldn't get any special treatment, and we should rely on a "display manager" similar to GDM/LightDM/SDDM, for instance. This would bring many benefits, the most prominent ones being multi-user setups for those who need it (e.g ## Zed Officially Publishes Builds for Linux DevFeed: [Zed Officially Publishes Builds for Linux]() Original publisher: [Read original article]() Author: Mikayla Maki Published: 2024-07-10T00:00:00Z Content type: release Language: en Sources: [Zed Industries - Blog]() Topics: [Linux](), [ide](), [Rust](), [GPU](), [Wayland](), [Flatpak]() Tags: [desktop](), [development](), [gpu](), [installation](), [linux](), [open-source](), [rust](), [wayland]() ### AI overview Zed announces officially published Linux builds for its open-source Rust code editor, with installation options for most Linux distributions. The team describes ongoing work across GPUs, distributions, window managers, Wayland, and X11. ### Source excerpt We've stabilized our Linux build, download it today! ## What You Need to Know About X11 Forwarding DevFeed: [What You Need to Know About X11 Forwarding]() Original publisher: [Read original article]() Author: info@goteleport.com (Brian Joerger) Published: 2022-07-14T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [Protocol (disambiguation)](), [ssh](), [OpenSSH](), [GUI](), [Unix](), [servers](), [Linux]() Tags: [blog-post](), [deep-dive](), [gui](), [ssh](), [unix](), [wayland]() ### AI overview This article explains X11 forwarding over SSH, including how X11 works, how X clients and servers communicate, and the security implications users should understand. ### Source excerpt In this blog post, we'll deep-dive into X11 Forwarding, explaining what X11 is and how it works under the hood. ## March and April 2021 round-up DevFeed: [March and April 2021 round-up]() Original publisher: [Read original article]() Author: Samuel Dionne-Riel Published: 2021-05-04T00:00:00Z Content type: news Language: en Sources: [Mobile NixOS news]() Topics: [Mobile](), [Pull Request](), [Wayland]() Tags: [mobile](), [updates](), [wayland]() ### AI overview This March-April 2021 Mobile NixOS project update reports 11 merged pull requests, progress toward Plasma Mobile and Phosh support in NixOS, and improvements for PinePhone and other devices. The period ended with support for 18 devices. ### Source excerpt This update is the sixteenth in a series of regular updates on the state of the project. Only changes that have been accepted and merged in Mobile NixOS are chronicled here. There's always more work currently in-progress. Notable changes During the two months 11 pull requests were merged. This sounds like there's not much that has been happening, but this is only half of the story. Plasma Mobile support in NixOS A good portion of my time has been spent working on adding support for Plasma Mobile in NixOS. The pull request needs some work still, as there are issues, mainly dealing with Wayland and Plasma integration with NixOS. With that said, a draft for a Mobile NixOS demo image using Plasma Mobile was also made. It relies on the NixOS changes. After all, Mobile NixOS is a superset composed on top of NixOS. I wouldn't recommend anyone to use it at the moment, but it's not a disaster. It's the final paper cuts, the final 10% that needs 90% of the work. It's close to being done, yet far from being over. Phosh support in NixOS Some community members, starting way back in May 2020, and even before, were working on their side on adding Phosh support in NixOS @zhaofengli ran the last mile in #121226, with the initial support for Phosh in NixOS. There is also an example configuration demo system for Phosh for Mobile NixOS. Since Phosh is already being built in Nixpkgs, you can take inspiration from that example configuration and start using it at this moment. I invite you to follow through to the different pull requests, and thank the involved individuals. Device-specific changes Pinephone improvements The kernel was updated (#321) Sound support was fixed (#337) Gadget mode was fixed (#340) Ports Support for one new device was merged in this period. Pine64 PineTab (pine64-pinetab) [@zhaofengli] (#331) Bringing the total of devices to 18. ## What is Mobian? DevFeed: [What is Mobian?]() Original publisher: [Read original article]() Author: Mobian team Published: 2021-02-18T00:00:00Z Content type: article Language: en Sources: [Mobian's Blog]() Topics: [Debian](), [Mobile](), [Software](), [Wayland]() Tags: [debian](), [devices](), [gui](), [mobile](), [patches](), [wayland]() ### AI overview The article explains that Mobian integrates standard Debian with phone-specific projects and modifications to create a mobile distribution for supported phones and tablets. It describes Mobian's effort to upstream changes, its software stack, project origins, volunteer community, and funding. ### Source excerpt Now that the Mobian CE is being sold, and Mobian becomes more popular, we are often asked in the support channel, "what and who is Mobian?" In the midst of action, we don't reflect upon this subject very often, but it is worth contemplating and summarizing. What is Mobian? Mobian aims to integrate the standard Debian distribution with Phone-specific projects and modifications in a distribution that works on certain mobile phones and tablets, such as the Pinephone, the Pinetab and the Librem 5. The idea is to minimize the Mobian specific pieces by "upstreaming" changes to the original projects as much as possible. To achieve this, we tread a delicate balance between carrying customized patches and packages that are required to make Mobian run well on its supported devices, while trying to push as many of these changes into upstream Debian. You could think of Mobian as a Debian Pure Blend, and indeed we aim at becoming one at some point in time. For the time being, we are focused on the same software stack that Purism uses for the Librem5, that is, wayland-ish, gnome-ish, modem manager-ish. Being based on the Phosh environment facilitates that, but of course it is perfectly possible to run Qt-based software. We have nothing against KDE and the plasma shell, and are contemplating whether, when and how we can support that too, but for the time being creating a single working GUI is enough of a challenge. Who is Mobian? It was founded by a-wai in order to make Debian running nicely on the Pinephone. Mobian's public outing occured on 14 May 2020 when Mobian was announced in this thread in the PINE64.org forum. a-wai is the founder and leader of the project. That having said, he has proven to be listening and acting upon the opinions of his fellow volunteers1. These volunteers are a loose and informal collection of people that have nagged @a-wai long enough until he invited them into the (not so secret) developers room, where they conspire to achieve world domination. All ## FOSDEM 2014 DevFeed: [FOSDEM 2014]() Original publisher: [Read original article]() Published: 2014-02-09T00:00:00Z Content type: opinion Language: en Sources: [Radek Pazdera]() Topics: [FOSDEM](), [Open Source](), [Wayland](), [samsung]() Tags: [conference](), [europe](), [fosdem](), [free](), [open-source](), [samsung](), [wayland]() ### AI overview A personal summary of attending FOSDEM 2014 in Brussels, covering the conference's free-software community, social events, talks, and discussions about Wayland, open-source projects, contribution policies, and software licenses. ### Source excerpt The best free and open source conference in Europe.