From: "S. Lockwood-Childs" <sjl@vctlabs.com>
To: gary@mlbassoc.com
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-browsser] chromium issues
Date: Mon, 18 Apr 2016 11:37:19 -0700 [thread overview]
Message-ID: <20160418183719.GA7939@vctlabs.com> (raw)
Sorry about not doing a threaded reply (I deleted the message, oops,
and couldn't find the message ID in the online archive).
> * When chromium starts, I get a message:
> "Google API keys are missing. Some functionality of chromium will be disabled"
> This seems to only be related to speech - should I worry about it?
Actually there are various google APIs that Chromium optionally uses but
require keys, list here
https://www.chromium.org/developers/how-tos/api-keys
For example translate is on the list, because Chromium can provide a
context menu that directly translates a web page instead of having to
go to translate.google.com. This won't work without a valid key.
If you just plan on using chromium as a normal browser without such
bells and whistles, don't worry about the keys and get rid of the
warning by setting them as blank when you start up chromium
export GOOGLE_API_KEY=" "
export GOOGLE_DEFAULT_CLIENT_ID=" "
export GOOGLE_DEFAULT_CLIENT_SECRET=" "
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748867#253
next reply other threads:[~2016-04-20 11:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 18:37 S. Lockwood-Childs [this message]
2016-04-22 17:23 ` [meta-browsser] chromium issues Trevor Woerner
2016-04-23 1:18 ` Gary Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160418183719.GA7939@vctlabs.com \
--to=sjl@vctlabs.com \
--cc=gary@mlbassoc.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.