Skip to content

install instructions for ChromeOS not working #10963

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
darkoverlordofdata opened this issue Jul 28, 2024 · 5 comments · Fixed by #12026
Closed

install instructions for ChromeOS not working #10963

darkoverlordofdata opened this issue Jul 28, 2024 · 5 comments · Fixed by #12026
Labels
from.page-issue Reported in a reader-filed concern

Comments

@darkoverlordofdata
Copy link

Page URL

https://docs.flutter.dev/get-started/install/chromeos/web

Page source

No response

Describe the problem

There is a failure in these instructions when I try to "install Chrome from the command line:

wget https://dl-ssl.google.com/linux/linux_signing_key.pub -O /tmp/google.pub
gpg --no-default-keyring \
        --keyring /etc/apt/keyrings/google-chrome.gpg \
        --import /tmp/google.pub
echo 'deb [arch=amd64 signed-by=/etc/apt/keyrings/google-chrome.gpg] http://dl.google.com/linux/chrome/deb/ stable main' | sudo tee /etc/apt/sources.list.d/google-chrome.list
sudo apt-get update -y; sudo apt-get install -y google-chrome-stable```

it returns this message:

W: GPG error: http://dl.google.com/linux/chrome/deb stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E88979FB9B30ACF2
E: The repository 'http://dl.google.com/linux/chrome/deb stable InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.


which then results in:

E: Unable to locate package google-chrome-stable


### Expected fix

It should not get an error, and google-chrome-stable should be installed


### Additional context

_No response_

### I would like to fix this problem.

- [ ] I will try and fix this problem on docs.flutter.dev.
@darkoverlordofdata darkoverlordofdata added the from.page-issue Reported in a reader-filed concern label Jul 28, 2024
@sfshaza2
Copy link
Contributor

@domesticmouse, can you test this?

@domesticmouse
Copy link
Contributor

I no longer have a ChromeOS device. I'm unsure who to hassle to get a device that isn't locked down with a Google profile.

@sfshaza2
Copy link
Contributor

@RedBrogdon, how can we address this issue?

@darkoverlordofdata
Copy link
Author

Can I ask why would it install a linux version of chrome when chromebook already runs chrome? I am able to use this manually, and the chromebrowser seems to open ok whan I do manual testing

@domesticmouse
Copy link
Contributor

Can I ask why would it install a linux version of chrome when chromebook already runs chrome? I am able to use this manually, and the chromebrowser seems to open ok whan I do manual testing

The Chrome in ChromeOS is not visible from inside the Linux VM that the Flutter DevTools are running inside.

By installing a Linux Chrome, the flutter tooling can debug running Flutter apps.

parlough added a commit that referenced this issue May 19, 2025
The work in #11911 will
eventually supersede these docs, but to ease that transition and make it
easier to review complete some preliminary cleanup and small fixes.

- Removes old includes that weren't used anymore recently landed changes
- Inlines use of most remaining includes to simplify maintenance and
eventual removal
- Remove various usages of liquidjs templating where unnecessary or
overcomplicated
- Removes some verbose terminal output where hard to keep up to date
- Removes some outdated/unlikely troubleshooting asides in favor of
linking to official, external docs.
- Removes a few mentions of specific software versions.

Contributes to #11911
Contributes to #11907
Fixes #11997
Closes #10963
Closes #10884
Resolves #10885
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
from.page-issue Reported in a reader-filed concern
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants