680 points by Bogdanp 172 days ago | 528 comments on HN
| Mild positive Editorial · v3.7· 2026-02-28 14:07:22 0
Summary Digital Freedom & Open Culture Advocates
This technical news article reports on KDE Project's launch of KDE Linux, a community-driven operating system distribution. The article engages moderately with UDHR themes of freedom of expression, education, cultural contribution, and international cooperation through its coverage of open source development values and practices. The journalism itself exemplifies freedom of information and expression in technology reporting.
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
The article exemplifies freedom of expression through detailed technical journalism. It reports on community software development with comprehensive information, enabling informed decision-making. The underlying KDE Linux philosophy opposes proprietary gatekeeping and promotes open information sharing.
FW Ratio: 57%
Observable Facts
Article provides detailed technical information with links to source code, presentation slides, and developer announcements.
The journalism demonstrates freedom of expression in technology reporting and analysis.
KDE project's public development (milestones, issue tracking, code repositories) is documented.
LWN provides comment threads enabling reader expression and dialogue.
Inferences
Technical journalism exemplifies freedom of expression in information dissemination about public projects.
Open source values underlying KDE Linux support freedom from information gatekeeping.
Public availability of development details supports freedom of information for community participation.
The article celebrates a technical and cultural achievement (KDE Linux distribution as scientific progress). It demonstrates commitment to open sharing of knowledge and recognizes creators by name. Scientific and technical advancement through open collaboration is central.
FW Ratio: 63%
Observable Facts
Article celebrates KDE Linux as a technical achievement representing modern Linux architecture.
Recognizes multiple creators and contributors by name and role.
Describes the project as demonstrating how developers want to distribute software.
Open source model enables broad participation in scientific and technical progress.
Article makes development and reasoning transparent to public.
Inferences
The article exemplifies support for cultural and scientific contribution to society.
Open source development model enables widespread participation in technical progress.
Public documentation of achievement supports values of cultural expression and knowledge sharing.
The article exemplifies right to education through detailed technical journalism. It educates readers about complex technical concepts (Btrfs, EROFS, systemd, architecture). LWN.net's entire business model is technical education. Open source philosophy supports knowledge accessibility.
The article describes KDE as a collaborative project with multiple international contributors organized under governance structures ('Council of elders'). This demonstrates freedom of association and collective action in open source development.
FW Ratio: 60%
Observable Facts
Article describes KDE Linux development as collaborative work of multiple named contributors.
Governance model includes community members as 'elders' with decision-making authority.
Contributors are recognized from diverse international backgrounds.
Inferences
Collaborative structure exemplifies freedom of association in technical governance.
The article celebrates collective action in open source development.
The article discusses open source architecture, user control through system customization, and transparent development, which support privacy protection through informed choice and reduced surveillance.
FW Ratio: 60%
Observable Facts
Article discusses KDE Linux design emphasizing user control through customizable containers (Distrobox).
Project provides source code transparency and development information publicly available.
The platform (LWN.net) does not employ aggressive tracking mechanisms.
Inferences
Open architecture and source transparency enable users to audit and control privacy exposure.
User customization capability supports autonomy and privacy protection through user agency.
The article discusses intellectual property and user rights in the open source context—users' ability to use, modify, and distribute software through Flatpak, custom builds via mkosi, and access to source repositories.
FW Ratio: 60%
Observable Facts
Article describes users' ability to create custom images using mkosi tool.
KDE Linux packages are sourced from open repositories accessible to users.
The distribution model enables user control and customization of software.
Inferences
Open source licensing supports intellectual property rights through user modification rights.
Transparency and customization capabilities protect user interests in software as a form of property.
The article describes KDE's governance with a 'Council of elders' model where major contributors have decision-making authority, embodying democratic principles in technical governance. Milestone trackers and issue tracking are publicly visible.
FW Ratio: 60%
Observable Facts
Article states KDE governance is described as a 'Council of elders' with major contributors as elders.
Project maintains public milestone trackers and issue tracking systems.
Harald Sitter has final decision authority, representing transparent leadership structure.
Inferences
Governance structure embodies democratic principles in technical decision-making.
Transparency of planning (public milestones, issues) enables community participation.
The article describes international collaboration in KDE project, with contributors from diverse backgrounds working together peacefully toward shared technical goals. International open source cooperation is presented as normative.
FW Ratio: 60%
Observable Facts
Article mentions contributors from multiple countries and backgrounds to KDE project.
KDE is described as international community collaborating on shared software.
Open source model inherently spans geographical and cultural boundaries.
Inferences
International technical collaboration demonstrates peaceful cooperation toward common goals.
Open source values promote shared global progress and mutual benefit.
The article acknowledges community responsibilities and interdependencies—reliance on Arch Linux and systemd, security concerns, update delays, and governance boundaries. Shows ethical awareness of duties to community.
FW Ratio: 57%
Observable Facts
Article acknowledges KDE Linux depends on Arch Linux and systemd.
Discusses security update delays as consequence of architectural choices.
Notes governance with final decision authority held by Harald Sitter.
Includes contingency planning if project fails (transition to different distro).
Inferences
Recognition of dependencies and limitations shows awareness of community responsibility.
Security considerations reflect ethical duties to users and community.
Contingency planning demonstrates responsibility for potential negative outcomes.
The article mentions business use cases and OEM installations, indicating KDE Linux supports economic and professional work contexts. Multiple distribution channels and community contributions are acknowledged.
FW Ratio: 60%
Observable Facts
Article mentions business use and OEM installations as intended use cases.
Describes professional desktop environment with productivity tools (Firefox, Kate, Konsole).
Discusses both volunteer and professional contributions to KDE development.
Inferences
Availability of business-capable OS supports work-related rights and economic participation.
Recognition of multiple contribution models (volunteer and professional) supports diverse work arrangements.
The article discusses KDE software distribution across multiple platforms and channels, supporting diverse employment and contribution models. Work in open source contexts is presented positively.
FW Ratio: 60%
Observable Facts
Article mentions distribution through Flathub, Snap, and Microsoft stores.
Acknowledges volunteer and professional contributions to the project.
Describes sustainable development model supporting long-term work.
Inferences
Multiple distribution channels support diverse economic models and employment.
The article elevates both volunteer and paid contributions as valued forms of work.
The article discusses KDE Linux as a professional-grade operating system suitable for business use and productive work, supporting economic participation and adequate standards of living.
FW Ratio: 60%
Observable Facts
Article identifies business use and OEM installations as intended deployment contexts.
Content does not explicitly engage with the preamble's foundational rhetoric about universal human rights and human dignity, though open source values implicitly align.
LWN.net enables free expression through journalism and public comment; the platform supports open discourse on technology. Subscriber paywall limits some access, reducing structural score.
LWN.net is fundamentally built on education mission, sharing technical knowledge; though paywall reduces universal access, commitment to education is strong.
LWN.net supports cultural and scientific activity through documentation and celebration of technical achievements. The platform enables scientific exchange.