Description of problem: account synchronization and other features relying on google api keys are not working in the current version of chromium-browser. reason for that is that the api keys from the spec file are ignored/not used due to a missing line-continuation escape on the configure line: [starts with some options....] use_system_libpng=true \ use_custom_libcxx=false \ closure_compile=false google_api_key="%{google_api_key}" \ google_default_client_id="%{google_default_client_id}" \ google_default_client_secret="%{google_default_client_secret}" Note the missing \ on the closure_compile line. Major severity as it's a regression and easy to fix.
Assigning to our registered chromium-browser-stable maintainer.
Assignee: bugsquad => cjwCC: (none) => marja11
I noticed this while preparing the mga6 update, it will be fixed in 73.0.3683.103-1 (maybe in less than 24h since it's building on the old build machines this time).
Status: NEW => ASSIGNED
Fixed with chromium-browser-stable-73.0.3683.103-1.mga7.
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED