CoreOS engineer at Red Hat :redhat:, Fedora Atomic Desktops maintainer (Silverblue :silverblue:, Kinoite :Kinoite:), KDE developer :kde: and KDE Apps maintainer on Flathub :flatpak:.
Mostly boosts about :linux:, :rust:, :golang:, :androidalt:, :fedora:, :redhat:, :kde:, :plasma:, :gnome:, :k8s:, :flatpak:, :Kinoite:, :silverblue:, systemd, security and some French politics.
Searchable via tootfinder (https://tootfinder.ch/).
He/him/his.
Kubewarden 1.26 is out! 🚀
Now you can run multiple policies from YAML locally with `kwctl`, and set custom rejection messages for your policies (while still having the default messages).
For these and more, have a look at our blog post!
https://www.kubewarden.io/blog/2025/06/kubewarden-1.26-release
Do you use a drawing tablet with Linux? You can share your device info in two easy steps - no coding skills required! 💙
Help KDE devs like @redstrate build driver support.
More info at:
https://github.com/linuxwacom/wacom-hid-descriptors?tab=readme-ov-file#contributing
#linux #tablet #wacom #huion #stylus #artwithopensource #kde #freesoftware
In the i686 discussion in #Fedora we currently hear quite a lot of voices in support for the Steam client, but not that much of other use cases.
If you have anything specific using i686 packages on Fedora, which is _not_ Steam, this is a good time to mention it, so that your use cases are not lost.
https://discussion.fedoraproject.org/t/f44-change-proposal-drop-i686-support-system-wide/156324
And please do not panic, it is a discussion, nothing is decided yet :)
#JeRecrute (mon équipe recrute) un ingénieur software pour travailler sur netobserv [1], et potentiellement d'autres produits liés, chez #redhat . #Remote possible. L'annonce est ici: [2] - n'hésitez pas si vous avez des questions!
Au programme: #golang, #ebpf, #opensource, #kubernetes ... Plus d'infos dans les liens 😉
[1] https://netobserv.io/about/
[2] https://redhat.wd5.myworkdayjobs.com/fr-CA/jobs/job/Raleigh/Senior-Software-Engineer---OpenShift-Networking_R-047995?q=network%20observability
KDE's new first-run experience is coming along nicely:
https://merritt.codes/blog/2025/06/24/2025/first-run-experience
My team at #redhat is looking for a software engineer to work on netobserv [1], and potentially other related projects: see https://redhat.wd5.myworkdayjobs.com/fr-CA/jobs/job/Raleigh/Senior-Software-Engineer---OpenShift-Networking_R-047995?q=network%20observability
Don't hesitate to reach out for any question!
“A strange game. The only winning move is not to play”
Had to write this in response to recent events at #GNOME. I hope the right people read this and take it to heart.
2️⃣1️⃣ Here's the 21st post highlighting key new features of the upcoming v258 release of systemd. #systemd258
Earlier in this series I already wrote about "userdb", systemd's user database logic, that extends the classic UNIX "struct passwd"-based user database in a flexible and powerful way, based on extensible JSON user records.
Besides implementing a Varlink-based IPC API there's also a second way to make user records available: there's a bunch of drop-in directories: /etc/userdb/, …
I also wrote an FAQ about the X11 Session removal.
https://blogs.gnome.org/alatiera/2025/06/23/x11-session-removal-faq/
@ClariNerd @emersion @david_chisnall @dvandal @strlcat do yourself a favor and don't believe in baseless conspiracy theories.
You are free to ask the vast amount of distribution why they switched and I'm sure you won't get a "because RH said so" ever.
People working at RH are even allowed to make upstream decisions against the company's own interest... it's even publicly documented.
There is nobody pulling the strings, seriously.
@david_chisnall @dvandal @strlcat @davidgerard@circumstances.run I have poured most hours of my last 10 years of life into listening to users and pushing things forward on Wayland even if I personally wouldn't need the feature. I really saddens me that someone would think that Wayland developers don't care.
We do care, but we only have a finite amount of time in our volunteer life. Yes, we don't copy-paste solutions from X11: we try to fully understand the problem space and do better. This does mean that coming to us with technical solutions rather than use-cases tends to be met with "please, explain why you need to do this?".
I don't really know what you mean when you say that we silence criticism. I've read enough in the past years to guarantee that it's not silenced. I appreciate constructive criticism better than rants, rants tend to demoralize me.
I am also saddened about the conspiracy that big corp deprecates X11 against the community's will. There is no single company with a monopoly here, please take a bit of time to look at Wayland developers' employers. Personally, I'm ex-SourceHut and now just a volunteer (my day job is unrelated: SNCF Réseau).
I've never said that X11 was deprecated, and I always tell people to use whatever works best for them. The only reason why X11 has less activity nowadays is because X11 lacks volunteers. (We severely lack volunteers on the Wayland side too.)
People, distros, communities move away from X11 if/when they collectively decide that they should. Nobody's pulling the strings here.
The street that my mum lives in is a one-way street, but wasn't marked as such on #Google Maps. This caused many drivers to drive the wrong way. I have tried to edit it on Google Maps (there is such functionality), but to no avail. No matter how often I submitted a change (with photos of street signs!), Google said "Sorry, we could not verify it".
Solution: Edit the street on #OpenStreetMap! A few months after I did this, Google seems to have stolen the data, as it regularly does, and now the street is correct in both datasets!
Maybe, as a bank, you should not be using a random library taken from the internet, with a single maintainer and some 100 stars, and make it a critical dependency of your banking operations.
Maybe, as a bank, your IT should write and maintain such a library and open source it.
Maybe, as a bank, you should not continue to use the first library, and do the second thing after the first library was able to take down critical parts of your infra the first time.
Because we live in a society, and as a bank, you should be contributing to it, too.
But then, what do I know.
I rarely subtoot, but when I do just to say: if an open source project that your commercial project depends on breaks something in your software stack, causing you trouble, no matter how much, that's your problem and your problem alone.
"The software is provided as is" is a part of OSS licenses for a reason, and unless we have a contract that says otherwise, I'm not part of your bloody "supply chain".
Nate Graham lays out the state of Plasma's X11 session, the short term plans, and how things will go in the future.
https://pointieststick.com/2025/06/21/about-plasmas-x11-session/
"This week in Plasma" brings the news that Discover's list views can now be navigated with the keyboard, and that we met another accessibility standard by improving the readability of graph axis labels, as well as of selected items in KRunner and Discover, among many other things.
https://blogs.kde.org/2025/06/21/this-week-in-plasma-plasma-6.4-has-arrived/
A new issue of #ThisWeekInGNOME is now online!
#205 Loading Films
https://thisweek.gnome.org/posts/2025/06/twig-205
2️⃣0️⃣ Here's the 20th post highlighting key new features of the upcoming v258 release of systemd. #systemd258
Kernel files systems learn new mount options all the time. Often one wants to enable an option in a graceful fashion: if the kernel is new enough and provides the mount option, use it – and if not, then not.
We ran into this problem when we enabled quota support on tmpfs (see other story in this series): only new kernels support it, old kernels do not.
#Via Trish Greenhalgh
@trishgreenhalgh
June 19, 2025, 12:22 PM
"Every summer, I repost this article DROWNING DOES NOT LOOK LIKE DROWNING. To date, I know of FOUR kids who were saved after someone who'd clicked on the link learnt how to spot actual drowning. Take time to read and pass on."
Joining us for #Akademy2025?
Help spread the word! Add our e-banners to your social media, blog, or website: https://akademy.kde.org/2025/banners/
Register now, if you haven’t already!
https://akademy.kde.org/2025/register/
