Needless to say the “repair system” did not work (it has never worked). System has reverted to 6.14-37, but the 6.17-14 kernel and all its garbage are still there. I am assuming “exit status 11” means its a segfault?
I tried manually installing the headers, but no joy. Seems to be a dependency conflict. I timeshifted back to yesterday’s image, and ran a clean and autoremove. I guess I will put updating on hold and try again in a few days.
Likely an issue with proprietary kernel modules.
Had a problem upgrading to 6.17 too. I use aptitude, which gives me the full dpkg output, which was more helpful.. discover should do that as well.
In any case for me the cause was virtualbox-dkms failing to build its modules with the new kernel. So I decided to uninstall virtualbox (didn’t use it for months anyway). An alternative might have been to look for an updated package from oracle.
For more details, you can run sudo pkcon update or (if that gives you the same useless error) sudo apt upgrade in konsole.
Thank you sir, that solved it.
I had forgotten that I also had to uninstall Vbox with the 6.14 kernel. Given that I have not used Vbox since installing that kernel, I nuked it again and am going to leave it nuked. You also bumped me into remembering that my wifi driver was a manual build and had not been updated since having to do the upgrade to 6.14, so I pulled in a new git before trying the update again.
Et voila! A shiny new 6.17.
I am starting to wonder if I am getting early onset alzheimers. Sheesh.
Much appreciated.