When I tried to sign in to sync, I always get a "Could't connect to server" or "Syn has stopped working". It seems that google has shutdown it's sync for chromium, whose sync server url is "https://clients4.google.com/chrome-sync/dev". The google-chrome's sync server url is "https://clients4.google.com/chrome-sync" works fine. This new ebuild change chromium's sync server url to google-chrome's during src_prepare(). Reproducible: Always
Created attachment 320568 [details] chromium-21.0.1180.57.ebuild
Comment on attachment 320568 [details] chromium-21.0.1180.57.ebuild --- usr/portage/www-client/chromium/chromium-21.0.1180.57.ebuild 2012-08-03 20:01:31.000000000 +0800 +++ root/overlay/www-client/chromium/chromium-21.0.1180.57.ebuild 2012-08-06 23:27:42.138827371 +0800 @@ -165,6 +165,13 @@ \! -path 'third_party/zlib/contrib/minizip/*' \ -delete || die + # Change the sync server url to the one chrome use + # Google chrome's sync server url is https://clients4.google.com/chrome-sync + # Chromium's sync server url is https://clients4.google.com/chrome-sync/dev + # But it's unknown why the chromium's server doesn't work + sed -i 's/chrome-sync\/dev/chrome-sync/g' \ + ${WORKDIR}/${P}/chrome/browser/sync/profile_sync_service.cc || die + local v8_bundled="$(chromium_bundled_v8_version)" local v8_installed="$(chromium_installed_v8_version)" einfo "V8 version: bundled - ${v8_bundled}; installed - ${v8_installed}"
Was this change announced somewhere?
I don't see any announcement from google saying that the sync for chromium has stop. But I'm having trouble using sync for chromium for several days. If it is a server corruption, it might not take several days to restore.
It seems to be working fine for me as-is. Have you tried using a fresh profile?
Yes, I deleted everything beginning with "." in my home directory, but It doesn't work.
Sync works well on the new version of chromium.
So just 21.0.1180.57 is affected? If so, I can request stabilization of the next version.
21.0.1180.77 works well, 21.0.1180.75 not tested
(In reply to comment #9) > 21.0.1180.77 works well, 21.0.1180.75 not tested Closing then.
