Screenshot of the error

Deleted: Screenshot_from_2018-02-23_21-21-39.png 270 KB

	Screenshot_from_2018-02-23_21-21-39.png 270 KB View Download

Unable to reproduce the isue on chrome reported version 64.0.3282.186 using Ubuntu 17.10 with steps mentioned below:
1) Reinstalled chrome and navigated to chrome://sync-internals
2) Passwords got synced

@Reporter:
Please find the attched screencast for your refernce and letus know if we missed anything in reproducing this issue, please provide your feedback on it which helps us in further triaging it. could you please Let us know is this issue specific to Linux Mint 18.2?

Thanks!

Deleted: 815293.mp4 4.6 MB

	815293.mp4 4.6 MB View Download

It seems to be only present on Mint.

I got a new Chromebook and password syncs just fine.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I have installed the program from the repository and the Chrome website.  Neither worked.

How many passwords do you have in your Google account?

492 according to sync.  The Chromebook version synced successfully

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Unable to reproduce the isue on chrome reported version 64.0.3282.186 using Ubuntu 17.10 and 14.04, hence forwarding it to Inhouse team for further triaging the same on other Linux OS flavors, hence adding TE-NeedsTriageFromHYD.

Thanks!

- Launch Chrome with --enable-logging --v=1 and then close it.
- There should be a log file "chrome_debug.log" in the parent directory of the profile path. You can see the profile path in chrome://version/
- Search for "Password storage detected" string and post this line and all the subsequent lines from password_store_factory.cc here. For example on my machine they are

[68156:68156:0227/114738.962608:VERBOSE1:key_storage_util_linux.cc(53)] Password storage detected desktop environment: CINNAMON
[68156:68156:0227/114738.962657:VERBOSE1:password_store_factory.cc(214)] Trying libsecret for password storage.
[68156:68156:0227/114738.974700:VERBOSE1:password_store_factory.cc(217)] Using libsecret keyring for password storage.

Weird.  Now it's working.  But here's the log

[3299:3299:0227/105942.027432:VERBOSE1:key_storage_util_linux.cc(53)] Password storage detected desktop environment: GNOME
[3299:3299:0227/105942.027503:VERBOSE1:password_store_factory.cc(214)] Trying libsecret for password storage.
[3299:3708:0227/105958.065565:VERBOSE1:key_storage_linux.cc(56)] OSCrypt using Libsecret as backend.
[3299:3299:0227/105958.065709:VERBOSE1:password_store_factory.cc(217)] Using libsecret keyring for password storage

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

That backend is slow. You have a lot of passwords and it takes considerable amount of time to push them all. What happened
- First time you started downloading the passwords and Sync decided that it took too long. Nevertheless, the passwords were saved.
- You restarted the browser and there was nothing to do. Sync just completed.

We plan in the long term to stop using the Keyring. Until that day the backend may still be slow.

I'm reassigning to tschumann@. I don't know why Sync actually needs a timeout in this case. If it's needed then you may consider to increase it for the passwords.

Able to reproduce the issue on Debian Rodate using chrome reported version-64.0.3282.186 as per the steps provided in C#0.

Observed error for the 'Passwords' section in chrome://sync-internals for the first install and reinstall too.

Same issue onserved from M60 builds to latest chrome version.Hence marking it as Untriaged to get it addressed.

Thanks..!

Deleted: 815293-Rodate.png 315 KB

	815293-Rodate.png 315 KB View Download

Your issue is completely different. What is the full text in the red cell?

Please attach the log that I mentioned in Comment #13. 

Closing as WontFix because of Needs-Feedback and no response in > 1 month. Feel free to reopen or report a new bug if this is still relevant or there is new information.

I have provided my feedback...