Bug 23269 - Cannot log in chromium since update to 67.0.3396.62
Summary: Cannot log in chromium since update to 67.0.3396.62
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Christiaan Welvaart
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-03 09:48 CEST by Jerome Quelin
Modified: 2018-07-12 06:13 CEST (History)
3 users (show)

See Also:
Source RPM: chromium-browser-stable
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Jerome Quelin 2018-07-03 09:48:08 CEST 
1. update chromium-browser from 62.0.3202.94 to 67.0.3396.62
2. try to log in (top right corner, or mail.google.com or any other google service)
3. enter email / password
4. get error

It's specifically this mageia chromium package that has a problem:
- it worked with 62.0.3202.94 but failed as soon as I updated it to 67.0.3396.62
- I tried to install chrome (from google official repository) and it works
- I tried to install a nightly build of chromium and it works

Currently, chromium is not useful and cannot be used given we do not have any sync of history / password / etc, and we cannot log in any google account (thus, no email browsing).

thanks, Jérôme
Comment 1 Jerome Quelin 2018-07-03 09:50:20 CEST 
forgot to mention: I tried to remove all cookies, I also tried to clean up the profile, and also by removing ~/.config/chromium and ~/.cache/chromium
==> still not working.

CC: (none) => jquelin

Comment 2 James Kerr 2018-07-03 10:25:17 CEST 
This may be related to the problem with the API key which affected minitube. See bug#23199

CC: (none) => jim

Comment 3 Jerome Quelin 2018-07-03 10:47:18 CEST 
According to http://svnweb.mageia.org/packages/cauldron/chromium-browser-stable/current/SPECS/chromium-browser-stable.spec?r1=1238247&r2=1238246&pathrev=1238247, the google API keys were changed yet the package has not been re-submitted (or the build failed).

Indeed, this is what is available on our repositories:
Version     : 67.0.3396.62
Release     : 1.mga6

==> the 2.mga6 isn't available. can we resubmit mkrel 2 for mga6 please? (and check build status)
thanks, Jérôme
Comment 4 Jerome Quelin 2018-07-03 11:47:08 CEST 
It works fine if I export the API keys as environment vars

$ export GOOGLE_API_KEY=AIzaSyDhhIHB_kQZodiWr8yDAm8E3GwEyiXmuDU
$ export GOOGLE_DEFAULT_CLIENT_ID="1039996407057-q599ngv7i6ni4sbkd2fsns30246r9s9v.apps.googleusercontent.com"
$ export GOOGLE_DEFAULT_CLIENT_SECRET=mRHXPjlS4cLpp1beCiXoYbLZ
$ chromium-browser
==> it works fine

definitely an api key problem
Comment 5 Marja Van Waes 2018-07-04 12:46:47 CEST 
Assigning to the registered maintainer.

Assignee: bugsquad => cjw
CC: (none) => marja11

Comment 6 Christiaan Welvaart 2018-07-06 07:06:23 CEST 
67.0.3396.87-2 is in mga6 updates-testing, see bug 23153
Comment 7 Jerome Quelin 2018-07-06 13:02:03 CEST 
tested 67.0.3396.87-2 is in mga6 updates-testing, works fine.
Comment 8 Christiaan Welvaart 2018-07-12 06:13:05 CEST 
Fixed with 67.0.3396.87-2 in mga6 updates.

Resolution: (none) => FIXED
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.