Hello, after updating KDE Neon Plasma from 6.5.5 to 6.7.3, I noticed that the bugs found in version 6.7.0 have been fixed. However, there’s still a bug—though it occurs only randomly—where the system displays a “password error” message when waking from sleep, even though I didn’t enter anything. As for detection—such as the MIPI webcam or a fingerprint reader—is there really nothing out there that can handle a clean, automatic installation? It’s a shame that such basic things make using Linux more of a hassle compared to Windows and macOS.
Kudos to the team and contributors for the work they’ve done.
Hello, since the 6.7.3 update, does Discover still sometimes cause USB device and storage notifications to appear? It’s brief and doesn’t cause a freeze, and this issue was already present in Plasma 6.7.0 but not in 6.5.5?
note : If I lock my session using Windows + L, the session locks correctly and there are no unlock errors. Is this message displayed specifically when waking from sleep?
Before updating Neon Plasma from 6.6.5 to 6.7.3, I was able to read an NTFS partition, but now when I use Dolphin, I get the message: “wrong fs type, bad option, bad superblock on /dev/nvmexxxxx, missing codepage or helper program, or other error?”
Do you know why this is happening, and what should I do to fix this problem
Ultimately, Linux is just like Windows—every update brings its own set of problems. This regression is frustrating; it’s always up to us to report the bugs. The Linux world is imperfect, just like everywhere else.
since the 6.7.3 update, does Discover still sometimes cause USB device and storage notifications to appear?
Yes, it’s still happening on 6.7.3. Intermittently with no reliable recipe (yet) to trigger it. I had it happen three times on a fresh update to 6.7.3 via Discover. After the needed reboot I was able to trigger the behavior twice by just launching Discover and once by hitting the “Refresh” button after Discover had launched.
I’ve never done a desktop recording before but I’ll try to get one showing the behavior if I can.
EDIT: I captured the behavior on a screen recording. Right now I have it as ~20 MB .webm and .mp4 files. Thinking the best place to post this is in the KDE Bug Tracker, any better suggestions?
This seems to be related to the Snap backend, I will wager. Snaps are actually mounted like drives, and I am guessing various update checking etc in Discover via its snap backend is triggering something in the automout system. The popup does not happen when the backend is removed.
Probably worth a bug report so people can know about it.
Hi, this morning I updated Neon using Discover. It found three updates: GNOME 50, TAR, and Aerion. It asked me to restart, so I did. Now Discover is glitching—it keeps prompting me to restart and install the updates, whether I exit the app or refresh the page. Same thing happens every time. Every day has its own problem.
Is the Discover issue resolved by the god Thor, or is it a miracle? Plus, that “restart” message after installing the updates—Discover checks and says “Up to date”
Discover is acting up again. After an update and a restart, Discover keeps prompting me to update and restart. Basically, every time I update, it gets stuck on that message. Weird, right? This latest Neon version is clearly unstable compared to 6.5.5, which I miss. Linux is nothing but problems and nothing is easy, just like an article I read today—those writers are really funny.
Unable to update 1 package
Error while installing package: installed linux-headers-7.0.0-28-generic package post-installation script subprocess returned error exit status 11
I have Discover settings identical to yours, but still getting that message every time. No snap and flatpak integration here and there is also no fw update available. And after just performing pkcon refresh & pkcon update at CLI.
We can all agree that this isn’t just happening to me! Strangely enough, all it takes is a new update for Discover to stop displaying that message? I’ve seen this happen three times. Anyway, I don’t have any problems or error messages when running the `pkcon update` command.
My update settings are the same as yours No snaps enabled, just Flapak packages installed
To sum up, Neon Plasma 6.7.3 has the same bugs as the initial 6.7.0 release: Discover not working properly? USB storage notifications popping up when using Discover? NTFS disk access no longer working, even though it worked perfectly in 6.5.5? The “incorrect password” message appearing after waking from hibernation, even though I didn’t enter anything?
Yesterday I read an article by a writer about his ZorinOS review, claiming that ZorinOS detects everything flawlessly and blah blah blah… that ZorinOS is as easy as Windows and requires no user intervention because it’s so magical, haha. My own test confirms that ZorinOS isn’t any better than the others! Maybe ZeroOS will do better when it comes out
Not everyone is seeing all of these, if any.
I have two systems, and do not see the Disks ands Devices popup happen on my laptop, but see it for a very brief moment on my PC. if it is a bother, it needs to be reported, if it hasn’t already. This is (imo) from the snap backend as snaps do involve mounting a virtual filesystem. Why my laptop does not show this, I can’t say. I don’t have any snaps installed on either. I suspect specific hardware is involved.
But otherwise, I see none of these things you see on both my computers.
I use suspend/sleep. not hibernation, though. Hibernation is also hardware-specific, and is at least partly why *buntu based systems do/did not have hibernation/suspend-to-disk enabled by default for ages now.
A tip for updating on the command line is to use apt directly, since pkcon hides a lot of apt’s messaging when there is an error.
And I have at least CUPS and Chromium installed as Snaps (I can see that when they update).
It could be a hardware issue where something triggers a USB hub (internal or external) to do a rescan or re-report of devices. I occasionally see this in my system log and I hear my scanner doing its initialization routine.
