A lacking ampersand locked some end users out of their Chromebooks

A key bug in a recent Chrome OS release (91..4472.147) still left some consumers bricked out of their Chromebooks. Reddit, in thanks study course, has previously spotted the situation. As some eagle-eyed people, including one “elitist_ferret” (initially spotted by Android Police), have pointed out, the dilemma appears to boil down to a lacking ampersand in Google’s code.

Especially, it seems that Google applied one “&” in a conditional statement in its Cryptohome VaultKeyset, instead than two “&&”, which is the “AND” operator in C++, breaking up the line. The mishap prevented Chrome OS from examining user passwords versus saved keys, as Ars Technica notes, and that still left some users unable to log in.

Google has not still responded to a ask for for remark.

The Chrome OS subreddit was knowledgeable of the bug in 91..4472.147 as early as the afternoon of July 19th. “The most current stable update is halting customers from logging in,” just one person wrote at 1:23PM ET. “We suggest that you DO NOT update right until additional detect.” A variety of people also began reporting bugs about that time — some complained that their units would not acknowledge their passwords, even though many others explained they couldn’t even get past the boot-up screen.

Google said that evening on its Client Treatment Portal that a option would be deployed by the end of the working day on July 21st, and proposed that users powerwash their units, roll back again to earlier Chrome OS builds, log in with Guest Method, or wait around for the resolve. By the following day, the enterprise experienced identified the challenge with the new make and experienced halted its rollout. On the 21st, it noted that a new edition (91..4472.167) was currently being rolled out.

“The rollout will step by step release to units above the upcoming number of days,” the update reads. “Affected units can login by way of Visitor Mode or an account that has not signed into the gadget.” As soon as impacted end users have correctly signed in, they can comply with the measures in Google’s Help Center to down load the latest update.

About the author: Joshua Parker

Tv maven. Twitter advocate. Hardcore troublemaker. General web guru. Professional problem solver.

Related Posts

Leave a Reply

Your email address will not be published. Required fields are marked *