After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 775908 - Chrome sync password change doesn't synchronise with key ring
Chrome sync password change doesn't synchronise with key ring
Status: RESOLVED OBSOLETE
Product: seahorse
Classification: Applications
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2016-12-09 21:42 UTC by steve.lorimer
Modified: 2018-08-03 19:52 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description steve.lorimer 2016-12-09 21:42:04 UTC
I recently changed my google account password. I have 2FA enabled.

Now every time I close Chrome and reopen it, Chrome account sync tells me "a recent change in your account means you need to log in again".

I enter my new password and 2FA token, and it logs in.

Now, however, every single web page I was logged into, including gmail and my work google account, as well as all the other sites, facebook, slack, github, bitbucket, confluence, messenger etc etc, are all logged out, and I have to log back in again.

I tried removing my account from Chrome and re-adding it. That didn't work.

Only after I had deleted all my keys from Seahorse's "Default keyring", and then relogin with everything, did sync work again.

Note that at the time I had auto-login enabled, which meant I kept on getting the "Unlock Login Keyring" popup. I'm not sure if this is a factor.

So somehow, either due to a bug in the "Passwords and Keys" app, or something to do with the keyring being unavailable if you have auto-login enabled, the password for Chrome sync is not updated.

I am using this on Ubuntu 16.04
Comment 1 GNOME Infrastructure Team 2018-08-03 19:52:23 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/seahorse/issues/155.