Getting the latest Plasma on a stable Ubuntu base with KDE neon

Why KDE neon exists

Many users want the newest features of KDE Plasma, Frameworks and Applications, but a traditional Ubuntu release freezes the desktop stack for months. Upgrading to a newer Ubuntu release every six months can introduce system‑wide changes that are unnecessary for a desktop workflow. KDE neon solves this by keeping the underlying Ubuntu LTS unchanged while delivering a continuously updated KDE stack.

How the rolling Plasma stack works

KDE neon uses the Ubuntu 22.04 LTS base (or the current LTS at the time of release) and adds its own repositories that provide Plasma, KDE Frameworks and Applications built from the upstream master branches. Because the base OS packages (kernel, libraries, system services) come directly from Ubuntu, they receive the usual LTS security updates and remain predictable. The neon repositories are pinned with a higher priority so that apt upgrade pulls newer Plasma packages without touching the Ubuntu version.

Worked example: upgrading Plasma

1. Open a terminal (you can do this from the application launcher or with Ctrl+Alt+T).
2. Update the package index:

   sudo apt update

   This contacts archive.neon.kde.org and the Ubuntu mirrors.
3. Upgrade installed packages:

   sudo apt upgrade

   You will see Plasma-related packages (e.g., plasma-desktop, plasma-workspace) listed for upgrade.
4. Confirm that the Ubuntu base has not changed:

   lsb_release -a

   The output should still show "Distributor ID: Ubuntu" and "Release: 22.04" (or whichever LTS is current).
5. Verify the new Plasma version:

   plasmashell --version

   Compare the version number to the latest stable release announced on the KDE website.

If you prefer to see exactly which versions are available, you can run

apt policy plasmashell

and look for the candidate version from the neon repository.

Trade‑offs and precautions

• Possible regressions: Because the KDE packages follow upstream master, an occasional update may introduce a bug that affects a specific workflow or hardware configuration.
• Monitoring: The neon project provides a "testing" channel where upcoming Plasma builds are published. Users who experience issues can temporarily switch to this channel or hold specific packages with sudo apt-mark hold plasmashell until a fix arrives.
• Third‑party compatibility: Applications or plugins compiled against an older Plasma ABI may need rebuilding after a major Plasma bump. Checking the application’s documentation or using the distribution’s built‑in compatibility packages can mitigate this.

What to do if an update breaks your session

1. Switch to a virtual console with Ctrl+Alt+F3 (or F2–F6). Log in with your username and password.
2. Attempt to restart the Plasma shell:

   plasmashell &

   If this fails, reinstall the core metapackage:

   sudo apt install --reinstall plasma-desktop

3. Return to the graphical session with Ctrl+Alt+F1 (or F7) and log in again.

These steps restore a functional desktop without requiring a full system reinstall.

Verification steps

• Confirm the base OS:

  lsb_release -a

  or inspect /etc/os-release for "UBUNTU_CODENAME=jammy" (or the current LTS).
• Confirm the Plasma version:

  plasmashell --version

  and compare it to the release notes on kde.org/announcements.
• Check that the neon repositories are active:

  grep -R archive.neon.kde.org /etc/apt/sources.list.d/

  or

  apt policy plasmashell | grep archive.neon.kde.org

  .

By following the example and verification steps above, you can enjoy the newest Plasma features while retaining the stability and long‑term support of an Ubuntu LTS base. If you encounter issues, the rollback and recovery procedures described here let you return to a working state quickly.