Password sync broken with profile w/ sync passphrase |
|||||||
Issue descriptionOS: Mac OS X I recently got the update to 59.0.3071.47 (Official Build) beta (64-bit) When chrome restarted the profile was out of sync, and I had to re-sign in and re-enter the sync passphrase. Furthermore: 1. I am logged out of all site (facebook, github, etc) 2. when I try to log in, the password autocompletion doesn't work anymore. Essentially looks like all my passwords are gone. This seems quite bad. I somehow suspect this is related with Issue 724869 and affects me because I have use a dedicated sync passphrase. Furthermore if I go to chrome://settings/clearBrowserData?search=cache to clear the cache, it says "Passwords: none". I seriously hope my passwords are not gone for real. Marking RB as this seems a major inconvenience for users.
,
May 22 2017
Since you did a browser restart, you're on OSX, and only passwords seem to be broken, this might be a Mac Keychain issue, +vasilii . The solution might be to delete your passwords file and restart Chrome again. See https://bugs.chromium.org/p/chromium/issues/detail?id=722607#c23 To get a feel for sync's health, can you take a screenshot or dump of chrome://sync-internals and we can take a look, my guess is that it'll show that the passwords sync service failed to initialize. If sync was enabled and healthy before you restarted Chrome, sync should still contain all your passwords. A custom passphrase stops passwords.google.com from understanding/returning your passwords, but within Chrome the decryption should continue to work just fine. Once the keychain issue is fixed sync will send all your saved passwords data to the passwords logic and things should return to normal.
,
May 22 2017
Was it an update from beta 59 to beta 59? Can you open the Keychain Access app and check the modification date of the Chrome Safe storage key?
,
May 22 2017
#2 sounds plausible. I don't have my personal laptop right now. However I realized that If I open my personal profile on my corp laptop (which runs canary) I see the passwords in chrome://settings. On the good side, it seems my passwords are there. I will confirm tonight when I get home. In any case, shouldn't we give a stronger signal to users and maybe point to instructions on how to solve keychain issues?
,
May 22 2017
+kerrnel@
,
May 22 2017
Removing RB as passwords haven't been lost. Re #3: was an update from beta (don't know the previous version) to beta 59
,
May 22 2017
,
May 22 2017
Do you know what version was installed before 59.0.3071.47? And indeed, can you please check the Keychain Access app and report the modification date of the Chrome Safe storage key?
,
May 22 2017
> Do you know what version was installed before 59.0.3071.47? No idea. To add excitement I was traveling for a week, so my laptop has been off for a week at least. Is there a way to tell my update history?
,
May 22 2017
If you ls /Applications/Google\ Chrome.app/Contents/Versions/ folder (or in your case the beta version), the two versions present should be the current version and the N-1 version. The modification date on the Chrome Safe Storage keychain entry might indicate more than the past version.
,
May 31 2017
This might have been related to a bug that causes reads of local password data to fail: crbug.com/728037
,
Jun 6 2017
Looks like there's been some development on issue 728037 , and it isn't widespread as we initially thought. Reading https://bugs.chromium.org/p/chromium/issues/detail?id=728037#c14 it seems that, regardless of which state you're in, the solution to both is to delete your passwords file, and then restart Chrome. OP, did you have a chance to check the files #10 asked for? Were you able to get back into a good state? Do we need to leave this bug open?
,
Jun 8 2017
,
Jun 12 2017
Sorry I forgot to followup here. It started working again at some point. sync-internals dump is here: https://drive.google.com/file/d/0B3KuDeqD-lVJaHFYQUtVcjBZWGc/view?usp=sharing
,
Jun 12 2017
Closing as things are working, feel free to re-open if things break like this again. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by primiano@chromium.org
, May 22 2017