Bug 28837 - Update request: Chromium (Google deny login)
Summary: Update request: Chromium (Google deny login)
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Christiaan Welvaart
QA Contact:
URL: https://www.mageialinux-online.org/fo...
Whiteboard: MGA7TOO MGA8TOO
Keywords:
Depends on: 28732
Blocks:
  Show dependency treegraph
 
Reported: 2021-04-25 14:33 CEST by Jean Michel Varvou
Modified: 2021-10-03 10:49 CEST (History)
6 users (show)

See Also:
Source RPM: chromium-browser-89.0.4389.128-1.mga8.x86_64.rpm
CVE:
Status comment:


Attachments
Mageia's packaged chromium is reported as insecure by Google (67.91 KB, image/png)
2021-04-25 16:14 CEST, Aurelien Oudelet
Details
Chromium google sign-in failure (21.54 KB, image/png)
2021-09-26 15:28 CEST, Rolf Pedersen
Details

Description Jean Michel Varvou 2021-04-25 14:33:37 CEST
Description of problem:
Impossible to connect to your google account with Chromium. It is therefore impossible to connect to gmail, to install extensions via the web store. Please note that we do not mention here the connection to synchronise your browser. We know that this feature has been removed on chromium.  The problem affects classic authentication to google services as it can be done by another browser. In the thread on MLO, we see that the problem affects several people. It is not present for the chromium version available under flatpak. 



Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Install Chromium
2.
3.
Comment 1 Morgan Leijström 2021-04-25 14:55:00 CEST
Is this supposed to work, or disabled by Google?

Do you propose we should ask users to use Chromium flatpak?

Or other method; packaged Firefox ESR, or Firefox flatpak?

CC: (none) => fri

Comment 2 Aurelien Oudelet 2021-04-25 16:14:12 CEST
Created attachment 12673 [details]
Mageia's packaged chromium is reported as insecure by Google

Connecting to Google services through Packaged version from Mageia of Chromium is considered insecure.
See attached screenshot.

CC: (none) => ouaurelien

Comment 3 Aurelien Oudelet 2021-04-25 16:28:55 CEST
Our packaged version is 89.0.4389.128

Note upstream is 90.0.4430.85, flatpak version is 90.0.4430.85.
We are outdated.

Not affected by this bug: flatpak version.


Assigning to packagers and committers.

Whiteboard: (none) => MGA7TOO MGA8TOO
Severity: normal => major
Version: 8 => Cauldron
Assignee: bugsquad => cjw
CC: (none) => nicolas.salguero
Depends on: (none) => 28732

Comment 4 Morgan Leijström 2021-04-25 19:25:34 CEST
Presuming update is enough

Summary: Impossible to connect to your google account with Chromium. => Update request: Chromium (Google deny login)

Comment 5 Aurelien Oudelet 2021-04-28 17:04:12 CEST
90.0.4430.93 released as flatpak on flathub.
Comment 6 Jean Michel Varvou 2021-05-01 12:12:36 CEST
nic80 notes the following changes between versions 88 and 89. 

"Some modules have disappeared between version 88 and 89.

Version 88:
webstore 0.2
CryptoTokenExtension 0.9.74
Cloud Print 0.1
Chromium PDF Viewer 1

Version 89 :
Chromium PDF Viewer 1

The startup options are also different (Active Field Trial Groups)

This can be seen by going to chrome://net-export , then running a save and viewing the file.

Where are the missing extensions (especially the cryptotokenextension)?

I couldn't find how to disable the cryptotokenextension to see if it could come from this module.

On the other hand, I found potentially another bug : the installation of Bless seems to forget a dependency : libglade2.0_0 ( without that Bless crashes at startup )"

cf : https://www.mageialinux-online.org/forum/topic-28866-2+chromium-devient-inutilisable.php
Comment 7 Jose Manuel López 2021-05-26 08:37:28 CEST
Any news here?? Chromium don't work fine still

CC: (none) => joselp

Comment 8 Rolf Pedersen 2021-05-26 17:16:57 CEST
Running chromium-browser-stable-89.0.4389.128-1.mga8 on 64-bit.  #METOO

For a long while, since this inability to log-in to google on this browser, I've just not used it.

CC: (none) => rolfpedersen

Comment 9 Christiaan Welvaart 2021-05-27 10:54:00 CEST
I did disable this cryptotoken at some point, so that may very well be the problem. I'll try a build without disabling it.
Vincent D 2021-09-09 17:33:10 CEST

CC: (none) => vincent.dema+mageia

Comment 10 Jean Michel Varvou 2021-09-26 07:49:25 CEST
CChristiaan

The problem is still there. Don't hesitate to contact me as soon as you think you will have a corrected version.

Thanks ;-)
Comment 11 Rolf Pedersen 2021-09-26 15:28:45 CEST
Created attachment 12933 [details]
Chromium google sign-in failure

To clarify and update my Comment #8, at the right of the Chrome address bar, there is a user chooser widget, where users can be added, switched, signed out, signed in.  In Chromium, this widget allows for adding and switching between users.  Authentication option is not available, that I can find.  Opening Gmail starts the google sign-in but, when my email is entered, the next page is similar to Arelien's screenshot.  That is the attachment.

[rolf@x570i ~]$ rpm -q chromium-browser-stable
chromium-browser-stable-89.0.4389.128-1.mga8

From About Chromium in the menu: 
Version 89.0.4389.128 (Developer Build) Mageia.Org 8 (64-bit)


[rolf@x570i ~]$ urpmq --sources chromium-browser-stable
http://mirrors.kernel.org/mageia/distrib/8/x86_64/media/core/release/chromium-browser-stable-88.0.4324.150-1.mga8.x86_64.rpm
http://mirrors.kernel.org/mageia/distrib/8/x86_64/media/core/updates/chromium-browser-stable-88.0.4324.182-1.mga8.x86_64.rpm
http://mirrors.kernel.org/mageia/distrib/8/x86_64/media/core/updates/chromium-browser-stable-89.0.4389.90-1.mga8.x86_64.rpm
http://mirrors.kernel.org/mageia/distrib/8/x86_64/media/core/updates/chromium-browser-stable-89.0.4389.128-1.mga8.x86_64.rpm
[rolf@x570i ~]$ Thanks.
Comment 12 Rolf Pedersen 2021-09-26 15:53:20 CEST
s/Arelien/Aurelien
Comment 13 Jean Michel Varvou 2021-10-03 10:49:18 CEST
Bravo ! You have done well. The bug is corrected for our greatest happiness. Thanks again for your investment!

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.