> 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 -- Dariusz Dwornikowski, Institute of Computing Science, Poznań University of Technology www.cs.put.poznan.pl/ddwornikowski/ room 2.7.2 BTiCW | tel. +48 61 665 29 41
signature.asc
Description: Digital signature
