"Google API keys are missing" error message won't go away no matter what I do
Reported by
smallcha...@gmail.com,
Oct 27 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3243.0 Safari/537.36 Steps to reproduce the problem: 1. Open Chromium, yellow error message appears across the top of my browser window. 2. Click on "X" in error message, error message disappears 3. Close and reopen Chromium, yellow error message pops up again 3. What is the expected behavior? I would like the error message to go away and stay away. What went wrong? I spent a lot of time on line trying to find a solution. But what I could find seemed to be oriented toward getting rid of the error message by installing the missing "keys" (whatever they are). The error message say some functionality [sic] of Chromium will be disabled. Whatever those functions are, I don't miss them. But that yellow error message is starting to get on my wick. Why doesn't it go away and stay away? Anm I doing something wrong? Is there something I can change in "settings" to quash/squash it? (NB: "function" is a noun, "functional," which has two connotations, one left over from a long defunct design movement called Functionalism and the one that is just the adjective form of the noun; "Functionality" is the adjective form of "function" - which is to say, if you use "functionality" in a sentence, you might not be as clear as you think you are.) Did this work before? N/A Chrome version: 64.0.3243.0 Channel: n/a OS Version: Studio 16.04 Flash Version: none - I tried lots of Flash versions and none of them work so I gave up on Flash No thank you.
,
Nov 2 2017
First of all, here is the Linux distro I am running currently (the
Ubuntu Studio version withe the re-time kernel)
Next, my attempt to install the latest Chrome Canary met with this
message from Google:
However, I did download the .deb, installed it using the GDebi
installer, and it seems to run just fine.
google-chrome-stable_current_amd64.deb
As I mentioned previous, I had repeatedly installed and then purged
Chromium by several different means. For this email, I purged Chromium
once more. Deciding to install Chromium by the method Ubuntu users were
most likely to use, I opened Ubuntu Software and was confronted with
these two choices:
The Chromium listed first was this version:
The bottom one with all the stars was this version:
Figuring that the 63.0.3223.8 version was newer than the 62.0.3202.75
version, I clicked on Install for the 63.0.3223.8 version.
When I started that version for the first time, and without changing any
defaults for installing any extensions or add ons, it came up with the
yellow Google API keys warning:
So I clicked on the X in the yellow warning to clear it.
Immediately after that I closed Chromium and restarted it and there was
the yellow waring again.
I hope this helps.
Thanks.
Charles Small
On 11/01/2017 05:43 AM, hdo… via monorail wrote:
,
Nov 2 2017
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 6 2017
Able to reproduce the issue on MAC 10.12.6, Windows 10 and Ubuntu 14.04 using chrome reported version #64.0.3243.0 and latest canary #64.0.3260.0. This is a non regression issue as it is observed from M50 old builds. Hence, marking it as untriaged to get more inputs from dev team. Thanks...!!
,
Sep 13
Archiving old bugs that haven't been actively assigned in over 180 days. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
,
Sep 13
Archiving old bugs that haven't been actively assigned in over 180 days. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks! |
||||
►
Sign in to add a comment |
||||
Comment 1 by hdodda@chromium.org
, Nov 1 2017Labels: Needs-Feedback Needs-Triage-M64