Google fixes single character “Chromebork” typo that prevented Chrome OS logins • The Register
Bug of the week Google fixed a bug in Chrome OS version 91.0.4472.165 that appeared on Monday and was preventing some users from logging into their systems.
Chrome OS downloads updates automatically but doesn’t apply them until restarting, so only those who restarted their Chromebooks to ingest the interrupted update were affected.
Earlier this week, the internet titan on his Google Workplace status page noted, “Our engineering team has identified an issue with Chrome OS 91.0.4472.165. Deployment of this version has been halted.”
As a workaround for those who have been bitten by the bug, Google has advised users: to “high pressure washing“their Chrome OS devices are reverting to factory settings; to restore the Chrome OS device to a previous version via USB; or to remove the affected account and add the account to the device. The three mitigation measures, however, erase local data on the device.
The programming error consists with a single missing character, an ampersand (&), which was inadvertently omitted in Chrome OS C ++ code. This oversight changed the logical AND (&&) operator in this conditional statement to a bitwise AND (&):
if (key_data_.has_value() && !key_data_->label().empty())
This means, on the one hand, that both sides of the conditional statement would be evaluated each time, rather than the right call to
empty() being done only if the left side
true. Either way, the omission of the ampersand changed the behavior of the Chrome OS code.
Google’s hotfix, Chrome OS 91.0.4472.167, was released on Wednesday and has been phased out according to Google’s release model.
“Affected devices can log in through guest mode or an account that has not logged into the device and follow the steps in this [Help Center] item to download the update, ”Google said.
This is the second update to Chrome OS version 91 to go wrong this month. A version update 91.0.4472.147, issued on June 30, 2021, proved problematic for certain hardware configurations, causing extreme CPU usage. Google rolled back the offending update about a week ago, but the problematic code still needs to be processed. ®