Hello, since updating to Neon Plasma 6.7, I’ve been experiencing several issues.
- Discover keeps searching for updates nonstop; it displays the number of updates found, but nothing else appears—not even the “Update” button?
- Discover triggers the USB storage device notification window when browsing through categories?
- apt update displays the following two errors in red:
Failed to start apt-news.service: Unit apt-news.service is masked.
Failed to start esm-cache.service: Unit esm-cache.service not found.
- When the system goes to sleep and the session is locked, I always get an unlock failure without having to enter anything; I’ve already encountered the same problem with Kubuntu 26.04, only worse—I had to shut down the PC
I should note that these issues also occur on a clean install, though I’ve never experienced them with Neon Plasma 6.6.5. The PC is set up for dual-boot with GRUB 2.12 and Windows 11.
Can you confirm these issues, and if so, please provide step-by-step instructions on how to resolve them?
By the way, will KDE Linux be able to perform a clean upgrade to the latest Neon version?
Thank you to the entire KDE team for your hard work. I’m eagerly awaiting KDE Linux—I’ve tested it, but I’d rather wait for the final release.
This appears to be a bug in the Snap plugin Discover. You can get around this by starting it using plasma-discover --backends packagekit. You can edit the menu entry to do this. Another option is to uninstall plasma-discover-backend-snap, which is a bit harsh if you actually use Snap packages. If you don’t, then it is perfectly safe to remove this as well as snapd.
This is cosmetic and is being looked at. Neon disables the messaging/“spam” seen in apt for Ubuntu Pro and the like in official Ubuntu Flavours, and my initial guess is there was an update on the Ubuntu side that is messing with things that needs to be adjusted on the neon side of things. Nothing is broken or anything here.
I have not seen any of the other things you are seeing.
No. KDE Linux is an entirely separate distro and platform than KDE neon.
Hi claydoh, regarding the bug with searching for updates using Discover: I don’t use Snap, and it’s not enabled in Settings. However, running the command `sudo plasma-discover --backends packagekit` launches Discover, and the update search works. On the other hand, in Settings, I no longer see the Flatpak and Snap sources. I tried disabling both of these sources, but the search still gets stuck?
As for the two xxx.services errors that appear with the `apt update` command, I’ll wait for the Ubuntu updates as you suggested.
There’s still the bug with the USB device notification that appears; I’ve noticed it also shows up when Discover starts up and when browsing categories.
Regarding the last bug about the session unlock error after waking from sleep, I’d like to add that this morning—and this is the first time it’s happened—the password field remained blank but the session opened anyway. It’s surprising and resembles what I experienced in Kubuntu 26.04, but more severe, which is why I switched back to Neon?
Thank you very much for your help, and I look forward to your response on the other points.
What’s clear is that I’ve been experiencing all these bugs since Plasma 6.7—they never occurred in version 6.5.5.
I’m experiencing the same thing here. Discover reports 6 updates available, but refuses to perform any update. Running sudo pkcon update results in no packages require updating to newer versions.
This doesn’t really seem to do anything, Discover launches, but still states 6 updates are available and refuses to progress any further.
EDIT: So it seems Discover is struggling with Flatpak’s, I just performed a flatpak update and I’m no longer being prompted that updates are available.
The “flatpak update” command worked this morning—4 successful updates, the same 4 I saw in Discover, which isn’t going any further. So Flatpak isn’t the cause. I ran these two commands: `sudo systemctl stop snapd.socket` and `sudo systemctl stop snapd`, but Discover still isn’t working when searching for updates? I think Snap is to blame. I’d like to verify this without uninstalling Snap. Do you have any ideas? And what about the other bugs, like the session unlock error when waking from sleep, and the USB storage notification that appears right after Discover starts up?
I’m asking this question to point out that everything was perfect before 6.7, so there are definitely bugs in this Plasma patch—kind of like Microsoft patches, right? So reporting these issues is the best way to move forward and get help from the KDE team
You could just uninstall the snap plugin for Discover - plasma-discover-backend-snap. This won’t remove snap at all, though you would need to manage them using the command line, or install the snap store. It does stop the perpetual ‘fetching’ screen.
No idea on these, I am not seeing them anywhere myself.
claydoh, are you running Neon on a virtual machine or on a physical computer? Just to remind you, yesterday I did a fresh install from the “neon-user-20260604-1324.iso” image and updated Plasma 6.7 via Discover, and I’ve noticed some glitches—nothing serious, thankfully.
In my experience, I find that Discover is less responsive than the previous version; I’ve noticed random delays in loading the categories I’m viewing, or even stranger things, like it taking 2 to 4 seconds to select or deselect a source? That’s just my personal opinion.
Hello, I finally reinstalled Neon Plasma 6.6.5 and am blocking the KDE update sources. Why did I make this choice? The command `sudo apt autoremove snap` caused a crash on reboot; I ended up with just the TTY console screen and nothing else—the desktop wouldn’t load. There are too many bugs, and I assume the Plasma 6.7 update also includes Framework and Qt, so I’m going to stay as I am, follow the Plasma 6.7 discussions, and wait for the stable version of KDE Linux. Just a quick aside: Neon 6.6.5 had none of the bugs I encountered with 6.7
I forgot something important that might not have anything to do with Plasma. In the six months I’ve been using Neon, I’ve never been able to get the webcam on my Dell Latitude 9420 to work—it’s an Intel IPU6 OVA01A MIPI module, I think—and I’ve tried several Linux distributions. How is it that these days, a simple webcam—which has become indispensable—is recognized in Windows without any extra steps, yet Linux can’t do the same? It’s hard to believe! I often read things like “Linux is easy…” blah, blah, blah, but I also read that Windows and macOS are still the best.
Hi, I’ve been using Plasma 6.5.5 for the past 4 days now, and I haven’t had any problems compared to Plasma 6.7. Discover is working properly, it’s more responsive when searching for updates and displaying categories, and there are no more bugs when waking from sleep or with session unlock errors—everything is perfect! I watched Claydoh’s tutorial on setting up an Intel IPU6 MIPI webcam, but I’m not too fond of all this mixing of versions, and the result never seems to work. Why do we have to go through so many steps just to set up a simple webcam or a fingerprint reader? The only way to get these components working is to start over with the Dell Ubuntu 20.04 recovery ISO, but I’m not sure how reliable that will be as updates roll out. Bottom line: if you want peace of mind and for everything to just work, you buy a brand-name PC with Linux pre-installed and stick with that old release for years—so where’s the “open source” in that!? We’re seeing the same practices as with Apple and Microsoft—they’re all in cahoots.
Oh, I see that this person ended up with a TTY console boot after updating to Plasma 6.7 but was able to get things working again with the help of daniel_Bull.
Just goes to show that 6.7 is unstable and there are more surprises to come!
