It probably means you have some left over data in /usr/lib/modules from kernels that are no longer installed.
It there anything in there that needs to be cleaned up?
This is likely because the kernel directories it is failing to find vmlinuz for are probably not your current kernels so the fact that it is failing is good.
I should, perhaps, be consuming those messages and not letting them show up as errors.
I donāt think that this is a direct problem, the hook @dalto is talking about wants to add a removed, and thus old/obsolete kernel, which obviously fails.
Not a problem for normal operating, so do nothing is the answer.
Thanks @fred666 - doing nothing is what Iām good at .
Iāve done some quick searches for āhooksā and what I may have done to mess them up, but have not found any real info yet. Will keep searching some more.
At least, the message is: itās nothing to worry about.
I wanna chaim in. I have also seen this āerrorā with every kernel update. However, since it never caused any problems, I didnāt pay any further attention to it. @SemLraug Itās great that you brought up this topic.
No hurry, no worry, but Iād be interested to know what it is, that you have to do to solve the issue, so, - if possible - could you give a heads up here when youāve been able to do your magic, so that I can mark this issue as solved?
Iāve also been getting those errors on kernel updates too lately and assumed it was just an annoyance message, since the update was trying to reinstall a kernel that was no longer present because it was just updated to the latest release, but Iām glad @dalto is on the case to correct the issue
.
