I just did an update to kernek 6.13.9 and all went OK
Then i opened htop and I saw that after updating the kernel, there was one last command persisting: mandb -q holding up my all 32 cores then the laptop froze.
Did hard reset! Unfortunately!
After restart, firefox profile broken (it was opened during the hard reset)
Thanks to the great devs for releasing the software without testing it.
You do realize that you have a sample size of 1 to claim that the kernel was released without testing and that this broke your system?
I can increase the sample size to 2 and tell you that it works fine on this laptop.
doesn’t prove anything!
keep increasing
I have edited the title to avoid panic for other users.
Thank you @liviu for your great contributions recently.
Hi @liviu
I’m sorry to hear about your problem.
I installed kernel 6.13.9 a few hours ago, and for me (an old laptop), it’s working perfectly fine.
I hope you manage to solve it :)
Regards
yeah, luckily using zfs, rollback of my entire home directory took 1 second.
I m just tired of fixing everyday what others break .
That is the whole point I was making with the “sample size 1” observation. Next time, you might want to consider that you just encountered a random issue before you get all confrontational and accuse developers of releasing untested code which caused some kind of data loss on your system.
Just to illustrate how ridiculous that claim is:
“Breaking news: I flipped a coin and we have all been lied to, coins only have one side and it is heads!”
Fine, I’ll humor you: I just upgraded my desktop as well, 6.13.9 works fine on that as well.
right, very random one, exactly after kernel update
intentionally I was watching what is happening using htop because I know when dnf finishes, there are stuff still going on.
keep wasting your time here but I’ll tell you one think: this forum is full of issues that come up EVERY SINGLE DAY!
does ring a bell?
On my old laptop where I can only use the installed 4GB of RAM, before kernel 6.13.9 I had experienced a modest increase in idle RAM usage of about 60/80MB. On a modern system this is insignificant, but on an old laptop it can make a difference. With kernel 6.13.9, the RAM consumption has returned to optimal levels.
Briefly, I want to express my appreciation for the Fedora forum. Compared to my experience with other communities (as I’ve been an active member in 4 forums), I’ve found the atmosphere here to be notably more constructive and peaceful, which makes discussion and finding solutions much more pleasant.
Furthermore, the quality and competence of the users’ responses have always been high, demonstrating a strong spirit of collaboration.
Thank you all for this positive and helpful environment.
Perhaps by moderating the terms and abandoning aggressive attitudes the forum could be appreciated more.
Ciao
Mauro
Fedora is a fast-moving distro, which means that issues will crop up. More than on, say, Debian stable, hopefully less than on Debian sid. And this is a forum, people come here if they have problems and are looking for solutions, not to share the stories of how wonderfully smooth their distro is working. There is going to be a bias in what you read here.
In any case, since you already seem to have it all figured out, I think you are right and I can spend my time better than to offer alternative explanations and different perspectives.
I just update two systems to 6.13.9 without issue, one ARM one X86.
Hi @liviu,
I just updated:
2 Laptops + 6 servers + 3 desktops without any issues …
Now, how about we address the real issue and quit beating people up in frustration
mandb -q holding up my all 32 cores
`
This has nothing to do with a kernel update/upgrade … it has to do with a man page/section upgrade/change that has caused a rebuild of the man pages database indexes. IF you have a slow HDD/CPU this process can saturate the system and cause it to stall a bit. All you need do is look up the process (ps -elf | grep mandb) and kill its PID (kill -15 {PID-of-mandb}) … then you can use the man pages for mandb for additional options to rebuild your man pages indexes/cache