KDE neon’s semi-rolling model: latest KDE on a frozen base
KDE neon pairs an Ubuntu LTS base with rolling KDE packages, but base upgrades require reinstall and PPAs can break apt pinning.
Loading…
ReadMeFeed / Community knowledge
#kde-plasma
Real questions. Useful conversations. Find the people who know your stack.
kdeneonKDE Neon Session Management: Verifying Wayland and Falling Back to X11
KDE Neon defaults to Plasma Wayland, but compatibility issues with NVIDIA, legacy X11 apps, or screen recording may require the X11 session. Learn how to check your current session and switch safely.
Enable KDE Plasma Wayland Session on KDE Neon
Step‑by‑step guide to switch KDE Neon from X11 to a Plasma Wayland session, including verification and rollback procedures.
Testing the Latest KDE Plasma with KDE Neon Snapshots
Learn how KDE Neon’s Snapshot feature lets you try nightly KDE Plasma builds, how to enable it safely, what to watch for, and how to verify or roll back to the stable repository.
KDE Neon: Staying on the Ubuntu LTS Base vs Chasing the Latest Plasma Repo
On a single KDE Neon machine I want to decide between two documented approaches: keeping the Ubuntu LTS base as the stable core with apt pinning preferring base packages, versus leaning harder on the KDE Neon user repository for the newest Plasma and KDE apps. The constraint is one machine that must balance security update cadence against feature freshness.
Signing into slack-desktop not working on 4.23.0 64-bit (Ubuntu)
In the app, going File > Workspace > Sign in to new workspace launches a browser window. After selecting the workspace in browser, it launches back a deep link back to slack but it doesn't work. Nothing happens on the slack-desktop. When inspecting the commands being run during the linking process it looks like KDE is modifying the link. What do I do t
slackEnable KDE Accessibility Framework by Default vs. Leave Disabled Until User Activation
Goal: Improve accessibility for KDE Neon users while balancing system performance and user experience. Constraint: The KDE Accessibility Framework (KDE AF) adds AT‑SPI2 support, screen‑reader hooks, and high‑contrast themes. Enabling it at boot increases startup time and memory usage, but keeping it disabled may delay discovery for visually impaired users, w