[ad_1]
A major bug in a recent version of Chrome OS (91.0.4472.147) left some users excluded from their Chromebooks. Reddit, in due course, has already spotted the problem. Like some eagle-eyed users, including an “elitist_ferret” (first spotted by Android Police), pointed out, the problem seems to boil down to a missing ampersand in Google’s code.
Specifically, it appears that Google used a “&” in a conditional statement in its Cryptohome VaultKeyset, rather than two “&&”, which is the “AND” operator in C ++, breaking the line. The crash prevented Chrome OS from verifying user passwords against stored keys because Ars Technica notes, and this prevented some users from signing in.
Google has yet to respond to a request for comment.
The Chrome OS subreddit was aware of the bug in 91.0.4472.147 as of the afternoon of July 19. “The latest stable update prevents users from signing in,” one user wrote at 1:23 pm ET. “We recommend that you DO NOT update until further notice.” A number of users also started reporting bugs around this time – some complained that their devices wouldn’t accept their passwords, while others said they couldn’t even get past the start screen.
Google said that evening on its customer service portal that a solution would be deployed by the end of the day on July 21 and recommended that users wash their devices powered on, revert to previous versions of Chrome OS. , log in in guest mode, or wait for the fix. The next day, the company identified the problem with the new construction and halted its deployment. On the 21st, he noticed that a new version (91.0.4472.167) was being deployed.
“The rollout will gradually be available on devices over the next few days,” the update said. “Affected devices can connect through guest mode or an account that has not signed in to the device. Once affected users have successfully logged in, they can follow the steps in the Google Help Center to download the latest update.
[ad_2]
Source link