Summary Open Source & Free Association Acknowledges
LWN publishes a technical news article reporting on KDE Linux, a new distribution released in alpha form by the KDE Project. The content implicitly engages with principles of freedom of expression through documented developer discourse and freedom of association through coverage of collaborative open-source development. The article is primarily technical reporting without explicit human rights advocacy.
To add something useful, OSes are the one area where reinventing the wheel leads to a lot of innovation.
It's a complete strip down and an opportunity to change or do things that previously had a lot of friction due to the amount of change that would occur.
> KDE Linux is Wayland-only; there is no X.org session and no plan to add one.
Does this mean they're testing that all the Wayland bugs are fixed? I haven't updated to the new Debian stable quite yet but all the previous times I've switch to Wayland under promises of "it's working now" I've been burned; hopefully dogfood helps.
> Unlike Fedora's image-based Atomic Desktops, KDE Linux does not supply a way for users to add packages to the base system. So, for example, users have no way to add packages with additional kernel modules.
But then, since / is rw and only /usr is read-only, it should be possible to install additional kernel modules, just not ones that live in /usr - unless /lib is symlinked to /usr/lib, as happens in a lot of distros these days.
Well, as long as they're either updating frequently or you're not using nvidia drivers (which are notoriously unpleasant with Wayland) I guess it's fine for a lot of people.
this bit is a no-go for me. they've decided what goes in the immutable base os and allowed a set of kde apps citing subpar experience flatpak versions. I'm guessing they haven't tested all flatpak apps as they tested their apps.
"Well, we’re kind of cheating a bit here. A couple KDE apps are shipped as Flatpaks, and the rest you download using Discover will be Flatpack’d as well, but we do ship Dolphin, Konsole, Ark, Spectacle, Discover, Info Center, System Settings, and some other System-level apps on the base image, rather than as Flatpaks.
The truth is, Flatpak is currently a pretty poor technology for system-level apps that want deep integration with the base system. We tried Dolphin and Konsole as Flatpaks for a while, but the user experience was just terrible."
How's Flatpak doing in terms of health of the tech and the project maintenance?
Merely 4 months ago things didn't look too bright... [1]
> work on the Flatpak project itself had stagnated, and that there were too few developers able to review and merge code beyond basic maintenance.
> "you will notice that it's not being actively developed anymore". There are people who maintain the code base and fix security issues, for example, but "bigger changes are not really happening anymore".
> KDE Linux is an immutable distribution that uses Arch Linux packages as its base, but Graham notes that it is "definitely not an 'Arch-based distro!'" Pacman is not included, and Arch is used only for the base operating system. Everything else, he said, is either compiled from source using KDE Builder or installed using Flatpak.
Funny; sounds more like a BSD (a prebuilt single-artifact Arch "base system" + KDE Builder-based "ports collection") than a Linux.
I wish them the best of luck. I never used Neon since it was a rolling release distro. This one I also won't be using because it immutable and relies on Flatpaks which are very buggy. Standalone binaries or AppImages are fine with me but Flatpaks and Snaps are garbage.
I love using KDE and use it on all my desktop machines. I even have a source compiled version ready to test / hack on if I need - utterly fun and easy to build using kde-builder and works on most distros including Ubuntu/Debian, Arch and Fedora.
That said, I don't think having yet another immutable distro is a great idea if they are only going to punt and use Flatpaks. They can run flatpaks on any distro out there. So not really understanding the idea behind this. Nothing really stands out from the article - they still need to make KDE work great with most other modern versions of the distros so it isn't like Flatpaks based KDE is going to give them an edge in having the best KDE on their own distro.
> KDE Linux is an immutable distribution that uses Arch Linux packages as its base, but Graham notes that it is ""definitely not an 'Arch-based distro!'"" Pacman is not included, and Arch is used only for the base operating system.
So it's basically a SteamOS sibling, just without Steam?
Without being too negative, I'd like to point out that Neon, ElementaryOS etc tried the same thing. A project thinks we need our own distro but ends up pulling resources away from improving the desktop environment itself.
GNOME doesn’t maintain Ubuntu or Fedora, but it still dominates the Linux desktop experience.
KDE made me fall in love with Linux. The familiar UI to Windows, the insane customizability, the snappiness - each and every one of their contributors are legendary.
If I'm able to do everything I can in my regular arch Linux installation, it would be nice to try an arch derivation that is immutable by design.
What I'm affraid is to start experimenting and finding more and more that my workflow is hindered either by some software not working because the architecture of the OS is incompatible, or by KDE UX design choices in the user interface.
That's not to say that it wouldn't be interesting, and it would say nothing about the quality of the software if I'd hit such walls, only that I'm not its target audience.
Does immutability mean something like ChromeOS, where you cannot install packages on the system itself, but you can create containers on which you can freely install software, including GUI?
If yes, what are some good options for someone looking for a replacement to ChromeOS Flex on an old but decent laptop?
I'm not a Linux user (yet) and I'd like to understand what "immutable" means here. Does it mean that I can't, eg, install Elixir or an IDE on it? I have absolutely no interest in deeply tuning the OS, which is why I'm interested here - I've been on Windows for decades for a reason. But if installing applications is blocked, or cumbersome, then who is this for?
The premise "we write software which is installed on operating systems, so we need our own operating system as well" doesn't make sense. Also the point that there are other operating systems like elementary or gnome OS out there is a moot point.
At least for elementary OS i kind of get the promise of some high quality user experience focused MacOS competitor.. But KDE OS? Why should I not just install KDE on my distro?
This distro doesn't seem to be born out of some real need for non-KDE-developers? Maybe it should be just some playground for KDE devs to test drive new tech?
Personally I'm interested in distros with an immutable base system. After decades of a lot of tinkering with all sorts of distros, I value a stable core more than anything else. If I want to tinker and/or install/compile packages I can do so in my $HOME folder.
In fact, this is what I've been doing in other distros, like Debian stable, nevertheless I have no real control of the few updates to the base system with side effects.
This is not the first immutable distro, but it comes from the people who develop my favourite desktop environment, so I'm tempted to give it a try. Especially as it looks more approachable than something like NixOS.
A few years ago I switched to KDE and the experience has been so absolutedly seamless and good, and the upgrade to Plasma 6 took some time to propagate down to distros it was well worth the wait!
It seems to be that a project like KDE might be in a very good position to make a very competitive distro simply because they are starting from the point of the user experience, the UI if you will. Think M$ windows, it IS GUI, and fully focused on how the user would use it (I'm thinking the days of XP and Win 7).
A KDE distro might be less encumbered with "X11 vs Wayland" or "flatpak vs <insert package manager name here>" discussions and can fully focus on the user experience that KDE/Plasma desktop brings!
Immutable distros today feel like someone read a CNCF "best of" publication and decided to throw it at desktop Linux to see what sticks. Not everyone wants to be a DevOps engineer.
I think the concept has promise (see: ChromeOS) but the execution today is still way too rough.
Note that it's not necessarily an "Arch distribution" in the sense you might expect:
> KDE Linux is an immutable distribution that uses Arch Linux packages as its base, but Graham notes that it is "definitely not an 'Arch-based distro!'" Pacman is not included, and Arch is used only for the base operating system. Everything else, he said, is either compiled from source using KDE Builder or installed using Flatpak.
I think "most" are fixed. I use quotes because I've seen people say they have issues that I have never run into myself.
I'm currently stuck on Windows for some old school .NET work, but otherwise have been running Wayland on either arch or fedora for 8 or so years, no real problems specific to Wayland. With that said, I've also always had X to fall back to for the odd program that absolutely only worked in an X session. At this point, though, I don't even recall what they were (probably something that didn't like running under Swaywm because wlroots), so even that might not be an issue.
What makes you say "the one area"? There are plenty of areas that have enough development friction / inertia such that the same principle applies. Even generally, I think the reason why people caution against reinventing the wheel isn't because it prevents innovation, but because it wastes time / incurs additional risk.
Nathan (who is a QA person with user-visible breakage ever-present on his mind) is talking about the alpha and the present-day situation, which naturally isn't set in stone. KDE is a Flatpak contributor. One of the little skunkworks projects within KDE Linux is even exploring further evolution of Flatpak that would allow putting Plasma itself into one, etc. This is an ongoing story, you shouldn't assume dogma.
I recently installed Debian 13 and went with the default partition sizes for /, /var, swap etc. I had two flatpaks installed and my entire /var partition was filled up with 10gb of flatpak data. Frankly very bad default partition sizes and I should not have been so trusting, but flatpak is an unbearably hot mess.
Not only is Arch also a rolling distro (despite them saying "not Arch!"), Arch is one of the most horrible rolling distros in terms of stability. Their general principle for package breakage is "you should have checked it on our (site) release log". They don't throw an error or a warning, if something is a breaking change and you pull it into your system, you basically get a "hehe should have checked the release log", and you're hosed.
If you want a good, actually professional rolling release, use SUSE Tumbleweed. They test packages more thoroughly, and they actually hold back breaking or buggy changes instead of the "lol read log and get fucked" policy.
I'm in a similar boat - i tried the Wayland session in Debian 10 and 11 and lasted less than a day; in Debian 12 i toughed it out for about a week before hitting a showstopper; but this time in Debian 13 i've used it since release without a single nit to pick.
The issue is that you are using Debian stable. Software quickly becomes out of date, sometimes by years, with the exception of security fixes and occasional backports.
Wayland, KDE, and several other pieces of software evolve rapidly. What may be broken in one release will very likely be fixed a few releases after the last debian stable release.
I'll run Debian on a server if I need predictability and stability with known issues. I won't run Debian on a desktop or workstation for the same reason.
Sounds like a good distro to use with your parents and grand parents, if they're not solely using iPads...
That might be their target audience.
What appeals to me about linux is the hackability and configurability. This takes it all away in some way, but that's not to say that they won't find a market for it.
Flatpak works pretty well. I try to prioritize my distribution's repositories but some software is not packaged. I've taken the easy way out and installed the flatpak. I guess I could go and package them, but I've been too lazy so far.
If a distribution is immutable (and thus omits the package manager) and pre-configured for a specific purpose (here, ensuring that KDE works), how much does the base really matter?
I find that I really like using an immutable distro with a custom image (built with github actions).
So I can really separate the system-level changes (in the image, version-controlled) from my user changes.
It's a nixos-like experience without using nix at all.
There have been a couple of things to have in mind, with my Bazzite installation, for creating users or adding groups for example, this pointed me to use systemd-sysusers but it was simple.
Has any distro ever promised that there are zero bugs in the software they use? I don’t particularly like Wayland but a lot of people have been using it for years at this point…
This is where I've been for the last 7 years. Very happy with it. I'm looking forward to an Arc Pro machine with SR-IOV GPU capability for VMs. That is pretty much my dream desktop, as much as I care to have one.
On a desktop, I nowadays actually somewhat prioritize flatpaks. I can get recent versions, sandboxing and the configs and data are always in standard locations with predictable naming. They can be installed for user in home dir without root and are easy to move over in case of OS reinstalls.
Gnome has its own distribution called Gnome OS. It’s based on Fedora Rawhide.
It actually looks a lot what KDE is shipping here except Gnome provides it as a reference system for their developers at the moment but it’s totally usable as a user if you want to.
It means the base system doesn't support individual package updates. Similar to a docker image, upgrading to the next version requires a complete base-image upgrade. In general, it shouldn't affect your ability to add additional software on top, but it may impact how you do so (e.g. Fedora Silverblue only allows Flatpak containers on top of the base OS).
Immutable here just means there is a base OS+libs that you don't touch. So now elixir or an ide would install in a sandbox with any needed libraries not included in that base instead of install all the libraries and stuff globally
Editorial Channel
What the content says
+0.25
Article 19Freedom of Expression
Medium Advocacy Framing
Editorial
+0.25
SETL
+0.16
Article documents technical expression and discourse; multiple developers present project vision; reader comments enable public engagement
Observable Facts
The article documents developers Nate Graham, Harald Sitter, Hadi Chokr, Lasath Fernando, and Justin Zobel presenting and discussing their software vision
Reader comments demonstrate public engagement with article analysis and exchange of technical perspectives
Inferences
Publication of developer perspectives demonstrates freedom of expression in technical journalism
Comment section enables readers to engage in free discussion and debate about technical implementation
+0.25
Article 20Assembly & Association
Medium Advocacy
Editorial
+0.25
SETL
+0.16
Article documents KDE as a collaborative open-source project built on voluntary association of developers
Observable Facts
Article describes KDE as 'a huge producer of software' with major contributions from multiple named developers
Governance is described as a 'Council of elders' model where major contributors hold decision-making authority
Inferences
Documented collaborative structure demonstrates principles of voluntary association toward shared goals
Open-source project model enables and depends upon freedom of association among developers
+0.10
Article 23Work & Equal Pay
Low
Editorial
+0.10
SETL
ND
Article acknowledges volunteer work and documents significant developer contributions and labor
Observable Facts
Article notes KDE neon is 'being held together by a heroic volunteer'
Multiple developers are credited with major contributions to KDE Linux project
Inferences
Recognition of volunteer labor suggests acknowledgment of human effort and contribution
Documentation of developer contributions implicitly recognizes software development as meaningful work
ND
PreamblePreamble
Article does not address foundational human dignity or universal rights principles
ND
Article 1Freedom, Equality, Brotherhood
No content addressing equality and dignity
ND
Article 2Non-Discrimination
No content addressing discrimination
ND
Article 3Life, Liberty, Security
No content addressing right to life, liberty, or security
ND
Article 4No Slavery
No content addressing slavery or servitude
ND
Article 5No Torture
No content addressing torture or cruel punishment
ND
Article 6Legal Personhood
No content addressing recognition as person before the law
ND
Article 7Equality Before Law
No content addressing equality before the law
ND
Article 8Right to Remedy
No content addressing effective remedy for violations
ND
Article 9No Arbitrary Detention
No content addressing arbitrary arrest or detention
ND
Article 10Fair Hearing
No content addressing fair and public trial
ND
Article 11Presumption of Innocence
No content addressing presumption of innocence
ND
Article 12Privacy
Technical discussion of system-level isolation mechanisms; not statement about privacy rights
ND
Article 13Freedom of Movement
No content addressing freedom of movement
ND
Article 14Asylum
No content addressing asylum
ND
Article 15Nationality
No content addressing nationality
ND
Article 16Marriage & Family
No content addressing family or marriage
ND
Article 17Property
No content addressing property rights
ND
Article 18Freedom of Thought
No content addressing freedom of thought, conscience, or religion
ND
Article 21Political Participation
Governance mentioned but not substantively addressed as democratic participation
ND
Article 22Social Security
No content addressing social security or economic rights
ND
Article 24Rest & Leisure
No content addressing rest, leisure, or working hours
ND
Article 25Standard of Living
No content addressing adequate standard of living
ND
Article 26Education
No content addressing education or learning rights
ND
Article 27Cultural Participation
No explicit content addressing cultural and scientific participation
ND
Article 28Social & International Order
No content addressing social and international order for rights
ND
Article 29Duties to Community
No content addressing community duties and responsibilities
ND
Article 30No Destruction of Rights
No content addressing prevention of rights destruction
Structural Channel
What the site does
+0.15
Article 19Freedom of Expression
Medium Advocacy Framing
Structural
+0.15
Context Modifier
ND
SETL
+0.16
LWN platform provides infrastructure for publishing analysis and facilitating technical discussion
+0.15
Article 20Assembly & Association
Medium Advocacy
Structural
+0.15
Context Modifier
ND
SETL
+0.16
KDE's collaborative infrastructure and governance enable and require freedom of association
ND
PreamblePreamble
Not applicable
ND
Article 1Freedom, Equality, Brotherhood
Not applicable
ND
Article 2Non-Discrimination
Not applicable
ND
Article 3Life, Liberty, Security
Not applicable
ND
Article 4No Slavery
Not applicable
ND
Article 5No Torture
Not applicable
ND
Article 6Legal Personhood
Not applicable
ND
Article 7Equality Before Law
Not applicable
ND
Article 8Right to Remedy
Not applicable
ND
Article 9No Arbitrary Detention
Not applicable
ND
Article 10Fair Hearing
Not applicable
ND
Article 11Presumption of Innocence
Not applicable
ND
Article 12Privacy
Not applicable
ND
Article 13Freedom of Movement
Not applicable
ND
Article 14Asylum
Not applicable
ND
Article 15Nationality
Not applicable
ND
Article 16Marriage & Family
Not applicable
ND
Article 17Property
Not applicable
ND
Article 18Freedom of Thought
Not applicable
ND
Article 21Political Participation
Not applicable
ND
Article 22Social Security
Not applicable
ND
Article 23Work & Equal Pay
Low
No structural implications regarding labor rights addressed
ND
Article 24Rest & Leisure
Not applicable
ND
Article 25Standard of Living
Not applicable
ND
Article 26Education
Not applicable
ND
Article 27Cultural Participation
Not applicable
ND
Article 28Social & International Order
Not applicable
ND
Article 29Duties to Community
Not applicable
ND
Article 30No Destruction of Rights
Not applicable
Supplementary Signals
Epistemic Quality
0.81
Propaganda Flags
0techniques detected
Solution Orientation
No data
Emotional Tone
No data
Stakeholder Voice
No data
Temporal Framing
No data
Geographic Scope
No data
Complexity
No data
Transparency
No data
Event Timeline
20 events
2026-02-26 12:19
dlq
Dead-lettered after 1 attempts: KDE launches its own distribution
--
2026-02-26 12:17
rate_limit
OpenRouter rate limited (429) model=llama-3.3-70b
--
2026-02-26 12:17
rate_limit
OpenRouter rate limited (429) model=llama-3.3-70b
--
2026-02-26 12:15
rate_limit
OpenRouter rate limited (429) model=llama-3.3-70b
--
2026-02-26 09:32
dlq
Dead-lettered after 1 attempts: KDE launches its own distribution
--
2026-02-26 09:19
credit_exhausted
Credit balance too low, retrying in 348s
--
2026-02-26 07:24
dlq
Dead-lettered after 1 attempts: KDE launches its own distribution
--
2026-02-26 07:24
dlq
Dead-lettered after 1 attempts: KDE launches its own distribution
--
2026-02-26 07:22
dlq
Dead-lettered after 1 attempts: KDE launches its own distribution
--
2026-02-26 07:18
dlq
Dead-lettered after 1 attempts: KDE launches its own distribution
--
2026-02-26 07:16
dlq
Dead-lettered after 1 attempts: KDE launches its own distribution
--
2026-02-26 07:16
dlq
Dead-lettered after 1 attempts: KDE launches its own distribution
--
2026-02-26 07:15
dlq
Dead-lettered after 1 attempts: KDE launches its own distribution
--
2026-02-26 07:14
credit_exhausted
Credit balance too low, retrying in 302s
--
2026-02-26 07:13
dlq
Dead-lettered after 1 attempts: KDE launches its own distribution
--
2026-02-26 07:13
dlq
Dead-lettered after 1 attempts: KDE launches its own distribution
--
2026-02-26 07:13
credit_exhausted
Credit balance too low, retrying in 332s
--
2026-02-26 07:12
dlq
Dead-lettered after 1 attempts: KDE launches its own distribution
--
2026-02-26 07:12
credit_exhausted
Credit balance too low, retrying in 296s
--
2026-02-26 07:10
dlq
Dead-lettered after 1 attempts: KDE launches its own distribution