Harald Sitter is a long-time KDE developer who previously also worked on the music player Amarok and the Linux distribution Kubuntu. He loves talking about the nitty-gritty details of technology and quietly focusing on making things more automated and reliable.
More than 3 years ago we had taken a step back from our Plasma LTS Edition. It never quite fit into way KDE neon works as a product, nor as a project. Plasma was caught in the past while the rest of the system kept rapidly leaping forward, resulting in a less than stellar user experience and a huge cost in maintenance. All the while it has always been the least used edition.
We have consequently decided to draw the only natural conclusion and end support for the KDE neon Plasma LTS edition on 2021-07-01.
For users that absolutely want to use Plasma LTS, we recommend that you instead look at one of the actual LTS distributions such as Kubuntu LTS or openSUSE Leap that try to maintain a stable system as a whole, not just the desktop.
If you would rather stick with neon, which we would of course prefer 💕, you’ll have to switch to the regular KDE neon User Edition. We have created a handy guide for this, available in the KDE UserBase Wiki.
A while ago we have talked to you about our plans to switch to offline updates, in an attempt at making the update experience more reliable.
After some testing we have now rolled out the change to all editions. For further details you can check out the previous blog post. As previously noted, this only affects the out of the box experience when using Plasma’s Discover for updates. Terminal applications and other GUIs are unaffected.
For a very long time we’ve been paving the road for offline updates. We are excited to finally introduce the first step to the KDE neon Unstable Edition today and would love to hear your opinion in the forum.
Unlike regular updates offline updates are not applied immediately but are only download and marked for installation on the next system restart. This has the tremendous advantage that you no longer need to interrupt whatever you are doing to update the system. They also prevent the system from entering a curious state of inconsistency resulting in an increased chance of bugs and crashes just after updating. Previously you might have been angrily looked at by Firefox, had Dolphin crash on you, or even got locked out of the session because the lockscreen jumped off a cliff after you applied an update. The reason for this is that most complex pieces of software really do not fare well if essential files change out from under it. Offline updates solve this problem by simply moving the installation stage to a time when the system is in a less vulnerable state.
What is changing exactly?
Starting today if you use Discover to update your KDE neon Unstable installation, instead of immediately applying the update it will download the package and notify you that you need to restart to complete the update. Upon starting the next time the update is finally applied.
Any other package management frontend will not perform offline updates. This most notably also includes the terminal interfaces pkcon and apt-get. Application distribution systems such as flatpak and snap are equally unaffected by this because they generally are not able to break the same way as system software can.
You can still choose to prepare an offline update using pkcon if you prefer using the terminal: pkcon update --only-download && pkcon offline-trigger
The newly released and extremely elegant Plasma 5.13 is now available in KDE neon User Edition. We’ve also gone ahead and included Qt 5.11 and KDE Frameworks 5.47 to get a billion bugs fixed and improve printing support.