Re: [oe] [meta-browsser] chromium issues
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 -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-browsser] chromium issues
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. -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-browsser] chromium issues
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 -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
