Grinning, at least now.
I wasn’t a few days ago. With the update to Chrome OS 78, I was feeling pretty good about reliability again. Then, I started to read about new features. If they were as good as the Accessibility Option that I had previously blogged about, this could be good.
One new feature, in particular, excited me. It was a setting for “Dark Mode”.
I’m a real fan of dark screen (green screen too but that’s not the point). I find it easier on the eye and hope that it saves on battery life as others have claimed. So, I was ready to check it out. Simply go to the Chrome Flags menu and change a setting.
I’ve seen this warning a million times and a million times I’ve ignored it. I think you know where this is headed, right? I applied the Dark Mode setting and rebooted as suggested.
And everything looked good. I logged in and the browser reloaded. I went to Twitter and it was fine. But then, I had already set it natively to show a Dark Mode. Let’s try something with a White Background.
We know what that means. The browser has crashed that tab. I reloaded to see it partially load and then crash again. It looks like the browser is attempting to load the original page, do some colour shifting, and then reload with the new colours.
I tried to go to the help page.
But I couldn’t. It’s a Google page and so has a nice white background and so crashes.
I did some searching on my phone and found a Reddit page Dark mode on ChromeOS 78 has broken my Chromebook. That post could have been written by me! That, and a couple of other similar pages, revealed the one and only solution. Do a Powerwash on your computer.
So, I tried to do that. Into Settings I went where I new the Powerwash option was. The problem?
It had a white background and wouldn’t load! So, no Powerwash here!
Supposedly, after a Powerwash, the next step is to go to the Terminal and enter a “rollback” command. I was getting desperate so just went to the rollback stage.
The message from Chrome OS sounded hopeful; I guess it either didn’t know that I couldn’t access the Powerwash button or didn’t care. So, I let it do its thing.
I expected to get a fresh Chromebook with no settings and a previous version of the Chrome Operating System.
What I did get kind of surprised me. I got the same Chrome OS version as what caused the problem but it did work. In fact, the customized settings that I had previously set were all gone and I was back to the defaults. Then, came in all the browser settings from my Google account. I did expect that although I probably could have gotten away without all the Android applications being reloaded. But, they came too.
The result? I have a nicely functioning Chromebook restored to Acer’s settings.
You’ve got to love the cloud.
Oh, and Happy Hallowe’en!