Final week, Google rolled out an incremental replace to Chrome OS 91 and it didn’t take lengthy for quite a few customers to start out reporting a critical bug that was crippling the CPU and various Chromebooks. The bug report, now triaged, has been up to date from precedence 3 to precedence 1 which is the second-highest degree that may be given to a however. Precedence 0 is generally reserved for bugs that expose critical safety points or utterly bork system functionalities. Whereas the bug has been acknowledged by Google and its builders, it’s nonetheless unclear as to what’s inflicting the difficulty or how far out we’re from a repair. Regardless of the problem, it’s critical sufficient that Google opted to pause the Chrome OS replace server quickly. Should you take a look at cros.tech, you’ll see that the present model out there for Chromebooks is 91.0.4472.114 which isn’t the identical model quantity that contained the CPU-crushing bug. The truth is, it’s the model of the earlier replace that rolled out on June 18. In case you are on the more moderen 91.0.4472.147 model and also you aren’t having points with excessive CPU utilization, you’re good to go. Nevertheless, should you haven’t up to date to the newer model or maybe you reverted to 91.0.4472.114, you might be in for an disagreeable shock if you attempt to set up the Linux container.AdvertisementsThis afternoon, I swapped Chromebooks with Robby so he can work on his evaluation of the Acer Spin 713 and he handed me an influence washer HP Chromebook Elite C1030. Once I logged in, I noticed that the Chromebook was on the older model of Chrome OS. No large deal till I attempted to launch my Linux container. After I set my space for storing and the set up course of started, I used to be greeted with a immediate telling me to replace Chrome OS to proceed. No biggie. I headed to the settings menu and clicked the replace button however I used to be promptly knowledgeable that my gadget was up-to-date.Doing my due diligence, I checked once more for an replace and went as far as to restart after which powerwash the Chromebook. No cube. The Linux container merely wouldn’t launch. I checked once more on one other gadget and positive sufficient, Linux won’t set up on a Chromebook with model 91.0.4472.114. My guess is that the Linux container remains to be in search of that newest model of Chrome OS which is ensuing within the immediate to replace. I’m positive that that is simply an unexpected facet impact of the paused Chrome OS replace nevertheless it may very well be a critical problem for customers needing to make the most of Linux purposes on their Chromebooks.AdvertisementsI was steward of Chrome OS and submitted suggestions to the builders and I will probably be opening a bug report shortly to deal with the difficulty. I’m assured that Google’s builders are already aware of the issue and hopefully, an replace to the Linux container is within the works whereas the workforce works to squash the CPU bug. Within the meantime, should you want Linux apps, you’ll have to get your self on a tool that’s both on the most recent model or already has Linux apps enabled. We’ll replace this submit as quickly as we see some motion on these bugs.