Hello, I just updated libc6 and a few other packages, and now I’m seeing that error in Discover again—one I hadn’t seen for the past 5 days.
Error while installing package: The post-installation script for the installed linux-headers-7.0.0-28-generic package returned an error with exit status 11
I had uninstalled this update and wasn’t seeing the error anymore, so I’m wondering how it could have reinstalled itself? I didn’t see it in the list of recent updates.
Digging a little bit deeper - there was still a firmware upgrade - “fwupdmgr get-upgrades” helped. So somehow Discover did not list it but still asked to reboot to install it but that failed as the update was not downloaded. After performing the update with fwupdmgr, the message in Discover disappeared.
Hello, I just booted up the latest Neon ISO, and as you probably know, the Linux kernel is version 7.0.0-28. That’s surprising—it’s precisely this update that’s been failing for several days on version 6.17, which I’m currently using. So it seems that KDE Neon has switched to the Linux kernel 7.0, but the update is failing. Too bad—I’ll have to reinstall KDE Neon. That’s not a big deal, and I prefer this approach to updates that don’t work and leave me with a messed-up system. It’s surprising that KDE Neon jumped straight to kernel 7.0 instead of 6.18, isn’t it?
Does anyone have anything to add?
Not really, this is what its Ubuntu base did.
Yes, this is strange.
Both of my Neon systems updated nicely.
hello krake, For your information, I no longer see the installation error for linux-headers-7.0.0-28-generic.
Here is what `apt list linux-headers-7.0.0-28-generic` displays:
Listing… Done
linux-headers-7.0.0-28-generic/noble-security,noble-updates,now 7.0.0-28.28~24.04.1 amd64 [installed, automatic]
Question: Why is the Linux kernel on my system still version 6.17? Do I need to wait for further updates to upgrade the kernel, or should I already have the Linux kernel 7.0.0-28 with this `linux-headers-7.0.0-28-generic` update?
No idea.
I didn’t follow the thread closely enough, maybe you changed something to work around the issue you had and now you need to explicitly install the newer kernel to get it working again.
Hello, I have a simple question. I’m going to reinstall Neon with the latest Linux kernel ISO 7.0.0-28. At the start of the installation, I’m given the choice between “Linux Generic” and “Linux OEM Manufacturer.” What do you recommend for my Dell Latitude 9420, especially given the issue I’ve had from the start with detecting and configuring the Intel MIPI IPU6 camera and fingerprint reader? I’ve always read that “Linux Generic” is the best choice.
My other question is about the OEM step: what information should I enter there, and why?
Linux Generic.
No idea what the OEM install does different but its name suggests it target’s OEMs (companies who ship Linux preinstalled).
Maybe it skips user name configuration and does that on first startup, etc
Good answer—I hadn’t thought of that, and I agree with you; it doesn’t apply to me!
Some news for everyone: I’ve finished installing Neon using the Linux kernel 7.0.0-28 and Plasma 7.6.3 ISO. Here’s what the `uname -r` command returns:
7.0.0-28-generic
So the persistent issues are back—they’ve been happening since the Neon Plasma 6.7.X version, but never with Neon kernel 6.XX and Plasma 6.5.5. Here’s what’s going on:
- An “USB storage” notification appears at startup and while browsing Discover.
- An “incorrect password” error appears when waking from sleep, even though I didn’t enter anything.
- Fixed the NTFS disk access issue
- Fixed the issue in Discover where it prompts for an update and reboot even though there isn’t one (to be monitored over time with this version)
- No notification for header-linux-7.0.0-28-generic—which is normal, you might say, in this latest version
I still need to get my Intel MIPI IUP6 camera and fingerprint reader working; they’re still not recognized in this recent version after installation and updates. It’s still strange after so many years—I’m not using a recent model, so I don’t understand this situation!?
Before I dive into these two tasks, does anyone have any help or a reliable tutorial?
For the USB storage notification at startup and when using Discover, I’ve disabled “Show notification badges,” “Discover tests,” and “More USB storage notifications” in System > Notifications > Discover. I’ve only checked “History” and “Contextual.” Is there a risk that I’ll miss a Discover alert or notification, and why does Discover behave this way when “Show notification badges” is checked?
I switched back to Discover too quickly; I’m still getting the “USB storage” notification. It’s no big deal, but it’s not normal, and I’m still getting the message to restart and install updates even though there aren’t any? Just to clarify and reiterate: with Neon Plasma 6.5.5, I never had these issues. There’s definitely something wrong with these new versions, and it’s not normal, especially since it’s the same device with multiple full installations and a full format.
If anyone can really help me install and set up my laptop camera and fingerprint reader—just a step-by-step guide on what I need to install and check— merci à tous
I haven’t installed anything on this new system or made any changes, so this is perfect for helping me install these two devices
This morning’s latest updates—GNOME 49/50 and I don’t know what else—forced me to re-enter my Wi-Fi password. Is that normal?
Good news—I’m running Plasma 6.7.4 and Linux kernel 7.0.0-28. Since this morning’s updates, I no longer get the “USB storage” notification when Discover starts up or while using it 
It seems the issue has been resolved; I’ll confirm this in a few days, along with the rest.
There definitely was a bug in Plasma.
I might have announced this a little too soon—I’m still getting the “USB storage” notification when I boot up and while using Discover 
Sorry
Why isn’t Firefox ESR included in the Discover software list? I only use this version because of its unique features and support, and I have to install it via the terminal; the pre-installed version is removed as soon as KDE Neon starts up for the first time.
As for the rest, there’s still that USB storage notification bug with Discover; I get the impression that the notification appears much less frequently, and there’s still that ‘incorrect password’ unlock error when the computer comes out of deep sleep whilst locked – though this doesn’t happen when it comes out of screen saver whilst locked.
Just kidding – am I ever going to see the Linux PluginPlay work as well as it does on Microsoft Windows for my camera and fingerprint reader? Do you think that’ll ever happen now that I’ve got KDE Neon with kernel 7.0.0-28 and Plasma 6.7.4?
Does anyone have any explanations for the persistent bugs, such as the ‘password’ error when unlocking the session after coming out of hibernation, or the ‘USB storage’ notification that pops up when launching and using Discover?
Usually it is much better since drivers come with the kernel and are thus pre-installed.
Sometimes this does not work as expected if the hardware vendor has submitted their driver too late before releasing their product or has not submitted a driver at all.
Obviously both situations are annoying, especially the latter as it then depends on some 3rd party to able and willing to do the HW vendor’s work.
As someone suggested earlier this seems to be cause by the interaction between Discover and Snap.
You could try deactivating the Snap source in the Discover settings, at least that seems to work for me since I have never seen this notification until recently when snapd itself got updated and needed to be restarted.