[Pkg-chromium-maint] Bug#748867: Fix/workaround for Google API key problem.

[Martin Steigerwald]

Am Montag, 13. Oktober 2014, 08:52:45 schrieb Dariusz Dwornikowski:
> > Another option is setting the Google API Keys in the environment [1].
> > 
> > So, it should be enough to create a file at /etc/chromium.d that
> > exports the keys. (/usr/bin/chromium sources all files on that dir)
> > 
> > This works for me:
> > 
> > $ cat /etc/chromium.d/googleapikeys
> > export GOOGLE_API_KEY="AIzaSyCkfPOPZXDKNn8hhgu3JrA62wIgC93d44k"
> > export GOOGLE_DEFAULT_CLIENT_ID="811574891467.apps.googleusercontent.com"
> > export GOOGLE_DEFAULT_CLIENT_SECRET="kdloedMFGdGla2P1zacGjAQh"
> 
> This approach fixes missing API keys for me too but chromium segfaults
> upon start (both with new and old .config/chromium). With this
> message:
> 
> [21725:21786:1013/085221:ERROR:get_updates_processor.cc(240)]
> PostClientToServerMessage() failed during GetUpdates

That sounds like a different bug. Please use this bug report only for the API 
key problem.

Thanks,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-chromium-maint/attachments/20141013/3fa43940/attachment.sig>