From: Gary Thomas <gary@mlbassoc.com>
To: OpenEmbedded Devel List <openembedded-devel@lists.openembedded.org>
Subject: [meta-browser] chromium issues
Date: Sat, 16 Apr 2016 08:29:16 +0200 [thread overview]
Message-ID: <5711DBBC.1070207@mlbassoc.com> (raw)
I'm having some issues with chromium on my i.MX6Q target. Using Poky/Yocto
meta = "master:20a0121b558b32179220e394a66cb90dc6ff3879"
meta-browser = "master:a67a3461a135668dba573183f0f62fcd5dfb3121"
meta-fsl-arm = "master:682b957545172a79cfb19108a9d0b61209f8671e"
meta-fsl-arm-extra = "master:39eb21c4c24a0be6d8277b566ebd52b657fbc2bb"
* 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?
* Accessing any page via https yields an SSL error. How do I fix it?
Note: firefox built from same layer on this target works fine.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
reply other threads:[~2016-04-16 6:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5711DBBC.1070207@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