Hey Jeff.. You seem very keen to place the blame on the person because you assume they themselves didn’t follow procedure and that it is impossible that perhaps there was a bug caused by the upgrade. Not sure if it is because you didn’t pay attention to what I said but I did say that in the end I had to remove things MANUALLY because doing the sudo dnf remove kernel*<Version>* procedure and all others that I found DID NOT WORK! I also did say that all these left overs like kernel 6.18.3 that 6.18.4 are things I noticed as I looked around further. It is only then that I confirmed with VILLY that I could remove the left overs from /boot/load/entries including those in /boot. Now if you want to continue believing that somehow I fucked up that is on you. I have never installed or removed a kernel before because I never had to.
Just a recommendation, before you make assumptions, ask first. Again to make sure you get it right this time, kernel updates only made it into my system via “dnf upgrade” and the issues I experienced and what I noticed I only saw them because I started noticing something weird things during boot time which I also reported in another post that someone else also experienced following an update
That is when I noticed 6.18.4 being in /boot but not in the /lib/modules and same for 6.18.3.
As for what I saw via dnf list --installed kernel* that was the exact content found in /lib/modules. 6.18.5, 6.18.6 and 6.18.7… I had to reinstall 6.18.6 because that was somehow NOT in /boot when it should have been.. And again I never tempered manually with those before.