New issue
Advanced search Search tips

Issue 864144 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Jul 16
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Crostini instructions direct me to chrome://settings which leads nowhere.

Project Member Reported by drchase@google.com, Jul 16

Issue description

Chrome version: 69.0.3475.0
OS: Chrome

Repro steps:
1. chrome://settings (from go/crostini-ui-instructions, step 2)
2. 
3. 

Expected: Settings
Actual: "This site can't be reached"

No doubt it is operator error, but I am following instructions, so it is really a bug in the instructions.  I have both Chrome and Chrome-dev on my Pixelbook, this is not called out as a potential problem but at this point I wonder if it is.

I haz a major sad, I really wanted to use Crostini.

 
please take a screenshot and attach it.  the error message described doesn't make sense.
Colleague points out that this is Chrome-for-android running on ChromeOS on Pixelbook, and the browser is operating as expected.  The problem is that I should have updated Chrome(OS), instead of updating Chrome(Browser).

So, this is a flaw in the Crostini instructions, that they don't warn against this mistake or give more detailed instructions on how to update ChromeOS (e.g. https://support.google.com/chromebook/answer/1086915 ).

By-the-way, the error message reported can be replicated on any Android phone, just open Chrome there and chrome://settings ("What happens if I do this on my phone?" was a big clue).
sorry, but i don't understand what you're referring to.  you're trying to run the Chrome browser inside of the ARC++ container and then do stuff in that ?  i'm not sure why you would ever bother running that browser.

as for versions, the docs already list a new enough version, and you're running that.
I don't know what ARC++ is so I can't answer that question.

The wrong browser was installed on the PixelBook using Google Play Store.
There were two browsers on the Pixelbook, Chrome (because ChromeOS), and (for Android) Chrome Dev.

The Android Chrome Dev browser had the required version number, but because it was an Android application, not ChromeOS, this as completely pointless.

The answer to "I'm not sure why" is because "confused" and "it was the nearest match to the Crostini instructions as written".  I think it is possible to write the instructions in a way that would result in less confusion, for instance including a link (e.g. see above) to how to put your Chromebook on the dev channel.

I am not (yet) running Crostini, I have the required version number, but apparently beta is not good enough because the option does not appear anywhere that I can find it.  If the dev channel is what required (and not just version number or better) it should say that.

Status: Fixed (was: Untriaged)
Updated to note that you need to go to chrome://settings in the built-in Chrome browser.

Sign in to add a comment