Comment 18 for bug 2028366

In the current situation, the user is not left with a broken DKMS package but a broken system because the kernel upgrade failed. This is really really bad. Not only is the kernel wrongly blamed when in fact it's a dkms issue but the system is in an utterly bad state and requires serious apt foo to recover. How can this be better than a fully upgraded system with a DKMS package that is not built for the current kernel?

We had ~50 reports (all dups of this bug) when people upgraded to Lunar. Most of the problematic DKMS are evdi, parallels-tools and realtek ethernet. Nothing boot essential.