After the second Ubuntu 18.04 update was delayed, Canonical has patched the bug affecting Linux Kernel 4.18 packages for Ubuntu 18.10 and Ubuntu 18.04 LTS.
The Kernel update released by Canonical on February 4 was available for Ubuntu 18.10, Ubuntu 18.04 LTS, and Ubuntu 14.04 LTS, but only Ubuntu 18.10 users were affected by the bug that prevented some computers with specific graphics chips from starting correctly.
“USN-3878-1 fix vulnerability in Linux kernel. Unfortunately, the update introduced a regression that prevented some systems with certain graphics chips from starting correctly. This update fixes the issues. We apologize for the inconvenience. Mention Canonical in a security advisory.
It is recommended that users update their systems automatically
The problem affects only Ubuntu 18.10 but also computers with Ubuntu 18.04 LTS Bionic Beaver running Linux Kernel 4.18 from Ubuntu 18.10, which will be included in the next Ubuntu 18.04.2 LTS release, delayed to February 14.
If you have Ubuntu 18.10 or Ubuntu 18.04 LTS with Linux Kernel 4.18 it is important that you update right now to linux-image 4.18.0-15.16 on Ubuntu 18.10 or linux-image 4.18.0-15.16 ~ 18.04.1 on Ubuntu 18.04 LTS. Follow the update instructions at this link.
Reading a previous article related to the Ubuntu boot problem in its last update I read that some users had managed to boot the system using an older kernel.
But thinking a bit, the following question arose: What would happen in a company that has implemented GNU / Linux for its computer processes, and that once all their computers have been updated (automatically), several dozen of them will present this problem?
Let's say, for example, that said company has 100 computers, and of which 60 suffer this failure.
Would each computer have to be configured individually to make it start again while the problem is fixed with a new update? If so ... what a job awaiting the sysadmin.
Well this happens in all the systems in the world from time to time, the difference is that in Ubuntu, fedora, centos, opensuse, redhat, gentoo, etc .. I mean in linux it happens very from time to time and it is corrected immediately, in windos the amount of computers are trying to start after an automatic update, I have seen it a lot of times, that is very rare in linux.
The good thing about this is that on Linux the community fixes problems fast.