Fresh install of Ubuntu 17.04 yesterday.

Installed Chrome. Signed in to Google account. Sync won't sync. After a while I get the following error.

Failed to start up the sync backend. Please make sure your network connection is working and if the problem persists, please sign out and sign in again to refresh your credentials.

So I sign out. Close Chrome. Open Chrome. Now I get the following error.

Profile error occurred Something went wrong when opening your profile. Some features may be unavailable.

I dismiss the pop up error and attempt to sign in again. Sometimes I can and other times I just get a blank screen where normally it would allow me to enter my email and password.

So I try:

  • Removing Chrome via terminal and doing a purge afterwards.
  • Manually removing the ~/.config/Google-Chrome folder.
  • Reinstall Chrome from a newly downloaded .deb installer.

And now I'm back to having issues with sync again. Done this two or three times and I still have issues.

I've logged out of Chrome on my Windows 10 laptop and log back in with no issues. So it isn't my network (obviously) and it isn't my account. I've used Chrome and it's syncing features on Ubuntu MATE with no issues.

I'm lost, any other spots config files or other files from Google Chrome may be hiding that I can delete?

I've also tired this with Chromium and Chrome Beta and I have the same issue.

closed as off-topic by David Foerster, Zanna, Eric Carvalho, Ravexina, user68186 Apr 25 '17 at 12:45

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "This describes a problem that can't be reproduced that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – David Foerster, Zanna, Eric Carvalho, Ravexina, user68186
If this question can be reworded to fit the rules in the help center, please edit the question.


I fixed it myself, was as simple as rebooting the computer. :D

  • Not sure why the question is off-topic as this answer fixed my problem. – OozeMeister Nov 3 '17 at 20:33
  • Fixed mine too, on 17.10. Using Chromium 65.0.3325.181. – Phil Cairns Apr 20 '18 at 19:44

Not the answer you're looking for? Browse other questions tagged or ask your own question.