Both issues are now resolved and updates were shipped to all 18.x point releases. Here's a summary of the situation.
Starting with kernel 4.15.0-20, a new package was introduced called linux-modules-extra-4.15.0-20-generic.
The update manager didn't know about it and didn't install it.
Other kernel packages such as linux-image-4.15.0-20-generic don't depend on it.
Although the system would boot correctly without it, this package is needed for some drivers to work properly.
Starting with kernel 4.15.0-20, the kernel postinst script (which is run during installation/upgrade) calls a command which only exists since linux-base 4.1.
On computers where the version of linux-base is still 4.0, this results in an installation/upgrade error and a kernel which isn't properly installed.
https://bugs.launchpad.net/ubuntu/+sour ... ug/1767133
To fix problem #1, the Update Manager now supports the new package names.
To fix problem #2, which should be fixed upstream eventually, the Update Manager depends on (linux-base >= 4.1).
The following updates prevent both problems from happening:
- mintupdate 18.104.22.168 in sarah
- mintupdate 22.214.171.124 in serena
- mintupdate 126.96.36.199 in sonya
- mintupdate 188.8.131.52 in sylvia
If one of these issues already impacted you. You can upgrade linux-base and install the missing linux-modules-extra-4.15.0-20-generic package.
Code: Select all
sudo apt-get install linux-modules-extra-4.15.0-20-generic
I'd like to thank everyone for their patience, and JeremyB in particular for catching our attention and providing help.
This is also a great opportunity to promote timeshift. Once you've got system snapshots in place, no matter what happens, you're just one restoration away from a working system.