The first time I open Google Chrome after login, it takes ages to load. When it finally loads I can close it out and it opens normally. What could be causing this, and how can I fix it?
Asked
Active
Viewed 5,802 times
4
-
file sync could be using up all of your cpu – ravery Jun 28 '17 at 07:43
-
@ravery Could you explain some more – Jun 28 '17 at 07:44
-
google cloud services are usually set to auto synchronize. thus when you login it compare local files to cloud files using up processor time. – ravery Jun 28 '17 at 07:46
-
1@ravery How do I fix this – Jun 28 '17 at 07:47
-
1turn off sync in preferences – ravery Jun 28 '17 at 07:49
-
@ravery If you add this as an answer I will set it as the accepted answer – Jun 28 '17 at 07:51
2 Answers
3
You might run into the problem where gnome-keyring-daemon
didn't start.
A workaround for me was to uninstall dbus-user-session
.

decocijo
- 278
-
1This was exactly the cause in my case. However I simply rebooted it (twice actually) and it fixed the issue. – Muhammad bin Yusrat Oct 22 '19 at 02:37
-
dbus-user-session
is a required package and will cause many unwanted side effects if removed. Kind of like swatting a fly with a Buick. – Dominic Cerisano Oct 19 '23 at 17:01
0
Google cloud auto-sync uses a lot of processor time.
Go to preferences and turn it off.

ravery
- 6,874