From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-browsser] chromium issues
Date: Sat, 23 Apr 2016 03:18:41 +0200 [thread overview]
Message-ID: <571ACD71.4040100@mlbassoc.com> (raw)
In-Reply-To: <20160422172327.GA32568@linux-yxv0>
On 2016-04-22 19:23, Trevor Woerner wrote:
> On Mon 2016-04-18 @ 11:37:19 AM, S. Lockwood-Childs wrote:
>> 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=" "
>
> Yes, that works. Or you could use the 'disable-api-keys-info-bar'
> packageconfig option too.
>
Thanks, that's good to know.
Any ideas on what to do about the SSL error (all https:// pages fail)?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2016-04-23 1:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 18:37 [meta-browsser] chromium issues S. Lockwood-Childs
2016-04-22 17:23 ` Trevor Woerner
2016-04-23 1:18 ` Gary Thomas [this message]
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=571ACD71.4040100@mlbassoc.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox