Matthias Klumpp

@matk
592 Followers
172 Following
376 Posts

Neuroscience PhD by day, free software developer by night. Debian Developer, KDE and GNOME member; working at @purism

Opinions are my own.

Bloghttps://blog.tenstral.net
GitHubhttps://github.com/ximion

The library works to abstract away platform differences by basically making Windows/MacOS/X11 emulate the zones concept from Wayland's xx-zones. That way, the same API works everywhere as long as only libwinpos is used (no mixing of coordinate spaces).

For a complex cross-platform multiwindow app, that was all that was needed for a pleasant experience on all platforms (unless you don't have xx-zones, unfortunately those users get a warning now and are directed at Xwayland as stop-gap solution).

I just made the first release of the now open-sourced LibWinpos today!
This #Qt library allows clients to set window positions on Mac/Windows/X11 and Wayland. It works for the latter if the #Wayland compositor implements the experimental `xx-zones` protocol or the kwin-zones plugin is used on #KWin.

The lib provides a single API for all platforms, graceful fallbacks, and is used in one internal proprietary project, as well as in one FOSS project now.

Find it at:
https://github.com/ximion/libwinpos

GitHub - ximion/libwinpos: Client window positioning hint support on Wayland

Client window positioning hint support on Wayland. Contribute to ximion/libwinpos development by creating an account on GitHub.

GitHub

hello #gnome folks! foundation elections have started:

https://discourse.gnome.org/t/gnome-foundation-board-of-directors-elections-2026/34884

1) make sure you have your membership!
2) please research your candidates!
3) run for elections!

GNOME Foundation Board of Directors Elections 2026

The GNOME Foundation Membership and Elections Committee are pleased to announce the upcoming elections for the Board of Directors in Spring 2026. The most important deadlines (UTC) in the timeline are the following: *GNOME Board Elections 2026* 2026-05-25: Announcements and list of candidates opens. 2026-06-08: Last day to announce candidacies, submit summary statements. 2026-06-08: Final list of candidates. 2026-06-15: Instructions mailed to eligible voters, voting begins. 2026-06-22: Vo...

GNOME Discourse

To port existing projects, all changes have been summarized (with examples, when possible!) in a small porting guide: https://syntalos.org/docs/porting-2to3/

Binaries are already available for Debian/Ubuntu in our APT repository (thanks to Cloudsmith for providing hosting services!).

Changes in this release are many and some deep refactoring has been done, with significant improvements in stability, speed and memory usage. Please test thoroughly anyway and report any bugs! :-)

Syntalos 2.x → 3.0 Porting

Syntalos 3.0 contains a small number of breaking changes that affect projects authored against the 2.x series. This page summarizes what changed and how to migrate existing setups. At a glance Stream types are now protocol-agnostic: LineCommand / LineReading replace FirmataControl / FirmataData. Hardware addressing in Line* is ID-based only: line_id replaces pin_id + pin_name. Python port helper APIs for Line* are redesigned as syl.HwOutputLine / syl.HwInputLine. Python modules declare their ports in code via register_input_port() / register_output_port(); the [ports] table in module.toml is gone. Signal block types are renamed to include their precision, and SignalBlockF32 is now a 32-bit float. The “Firmata User Control” (firmata-userctl) module has been renamed to “Manual Line Control” (hwline-userctl). Public C/C++ APIs (libsyntalos-mlink, -datactl) no longer depend on Qt. Out-of-tree C++ modules need to be ported and rebuilt against the new headers. 1. Porting Python modules & PyScript scripts Port types Anywhere your Python module’s port editor had FirmataControl or FirmataData selected, switch to LineCommand / LineReading.

#Syntalos 3.0.0 is out, for all of your scientific data acquisition needs!
This version drops Qt from all public interfaces (allowing wider use of its API), has a rewritten Python interface, rewritten IPC (using #iceoryx2), support for more scientific hardware, and a new network interface to manage a fleet of machines running one experiment.

This release has breaking changes, existing projects may need adjustments!

Get it at: https://syntalos.org/
Changes: https://syntalos.org/get/changes/

Syntalos

The pilot program bridges this gap by supporting a cohort of open source maintainers to participate in standards work at the @ietf @w3c and ISO. It provides training, mentoring, compensation, onboarding and on-site meetings at standards development organizations.

Applications for the first cohort are open until 19 May 2026.

(3/4)

Just to add: I do not blame RustDesk at all, it's a fantastic piece of software and the only thing that would have worked with Wayland (I would have floated the idea to move to it and away from AnyDesk for all systems, if it had worked). But both it and KRDP failed on this particular network, the latter not even showing any kind of error message (really weird experience, as there's just UI elements missing suddenly).

And all of these unattended-access tools will improve for Wayland still 🙂

Background is a new system that's running on Kubuntu 26.04 now. I tried for 2h to get RustDesk to work to keep people on Wayland, ran half of the apps through Xwayland so their windows end up in the right spots etc...

But now, for the scientists, Wayland is the thing that "doesn't work and Matthias tried to fix for hours" while switching to X11 solved all problems they had immediately. We really need to do better for these environments, especially people migrating...

Just had to switch another system at a research lab from Plasma Wayland to X11 for the customers - the reason? Remote desktop and multi-window positioning. #RustDesk did not work on that network, and they were using #AnyDesk with Windows machines anyway, which has no Wayland support.

And they were very annoyed that scientific apps did not position windows at the usual spots and predictably.

Really not a good impression, and a pretty bad migration experience still 😕

Thanks to the Red Team of Deutsche Telekom Security GmbH for finding and reporting this issue, and all the package maintainers who worked to ensure fixes are ready and shipped today.

If you are using Arch, Debian, Ubuntu or Fedora, you should already have updates waiting.

Please keep in mind that while PackageKit is commonly a desktop component, it is also often present via management software on servers. So if you are on a non-atomic distro, please update in any case!