I’m not having any issues running the latest kernel (kernel-core-6.10.3-200.fc40), but i did notice this line in the logs about the key signing. I was wondering if any others here also have that?
fedora abrt-server[45796]: Package 'kernel-core' isn't signed with proper key
Looks like there are some bugs already filed.
Looks like it was reported against rawhide over 2 months ago, it feels kind of bad that those kinds of issues can still trickle down to Workstation.
Similarly it seems there have been a lot of kernel related issues bugging people on the forums lately, hopefully there will be a bit more focus on stability going forward.
Remember that you only see reports from people that have issues.
You do not hear from people where everything just-works.
All my systems running Fedora just work and I update to the new kernels all the time.
Stability is accomplished by identifying issues then fixing them.
Activity in that respect is normal and users must report the problems before they can be found and fixed.
While delays in fixing bugs are inevitable, the trickle down is not an indication of lack of care, but rather that the issue is not severe enough to warrant limiting progress.
As noted above, the only reports you see are about problems, not the 99.9+% of users who are problem free.
When i see things like all the Macbooks losing wifi because of a wpa_supplicant update, i can’t help but wonder if not more can be done to prevent something like that from happening on such a scale. Similarly there are a ton of threads lately about non booting kernels with Nvidia. It’s just a noticeable amount.
I personally was also lucky since i didn’t have any serious issues myself.
Similarly you only see reports from people who have accounts here and take the time to post about their issues and try to debug them.
It would be fallacious to assume that people who don’t post here have no problems. You do not hear from people who are just stuck with a non-booting computer or one without wifi and decide to move away from Fedora, which could be most of the non-expert crowd. We don’t know.
Many people are putting linux on older systems when proprietary OS’s drop support, so linux is expected to support an ever increasing diversity (new systems being introduced, legacy systems being used long after commercial OS support ended). I have often encountered bugs affecting older systems introduced with updates. Most get fixed soon after someone provides a good bug report, but WiFi, Bluetooth, and audio are often affected so for critical systems it is important to have aiternative hardware (e.g., USB dongles) that can be used while waiting for a fix or until older hardware is replaced.
A bug that was introduced and fixed as soon as it was identified.
Those who updated (and had the affected hardware) while that package version was current were affected. Those who had different hardware or did not update at that time were not.
This is how many bugs are identified since the developers cannot possibly have all the hardware and software configs that users might have so not all situations can be tested until users actually see the updated packages.
Exactly, you do not have statistics and neither do we.
I’ll mark @grumpey’s reaction as the Solution to the thread, and let’s leave it at that.