I am on FreeBSD 12.1 amd64. Yesterday I installed the chromium package. On starting Chromium, I signed in to my Google account and turned on sync. But the browser failed to sync my passwords/theme/extensions. Today, I deleted the chromium package. Then I updated my ports tree and built the www/chromium port. But the browser still fails to sync. To be double sure that this is a FreeBSD issue, I booted into Linux Mint and installed chromium-browser. On turning on sync, the browser immediately synced my passwords/theme/extensions.
I am seeing the same issue: Version 79.0.3945.130 (Official Build) (64-bit) truss output if it is helpful: https://gist.github.com/codedmart/591954c5e63c8c37c9758df9241acf27
Me too, I wonder if it's a problem with the API key used by the FreeBSD project?
I'm having the same issue. Not sure which logs would be useful since chrome://sync-internals is showing all counters at 0 Also there's a forum thread - https://forums.freebsd.org/threads/chrome-sync-not-working.73991
OpenBSD was suffering from the same issue. The fix is here: https://marc.info/?l=openbsd-ports-cvs&m=159289397828827&w=2
A commit references this bug: Author: jrm Date: Fri Jun 26 00:43:52 UTC 2020 New revision: 540411 URL: https://svnweb.freebsd.org/changeset/ports/540411 Log: www/chromium: Update to 83.0.4103.106 and fix synchronization PR: 244185, 246387 Reported by: bourne.identity@hotmail.com Approved by: chromium@ (rene), cem Obtained from: Robert Nagy via OpenBSD port MFH: 2020Q2 Security: https://www.vuxml.org/freebsd/6a5d15b6-b661-11ea-8015-e09467587c17.html Differential Revision: https://reviews.freebsd.org/D25449 Changes: head/www/chromium/Makefile head/www/chromium/distinfo head/www/chromium/files/patch-base_system_sys__info.cc head/www/chromium/files/patch-base_system_sys__info__freebsd.cc head/www/chromium/files/patch-components_sync__device__info_device__info__sync__bridge.cc
A fix was applied based on Robert Nagy's work on the OpenBSD port. Please re-open if necessary.
A commit references this bug: Author: jrm Date: Fri Jun 26 08:44:33 UTC 2020 New revision: 540450 URL: https://svnweb.freebsd.org/changeset/ports/540450 Log: MFH: r540411 www/chromium: Update to 83.0.4103.106 and fix synchronization PR: 244185, 246387 Reported by: bourne.identity@hotmail.com Approved by: ports-secteam (implicit), chromium@ (rene), cem Obtained from: Robert Nagy via OpenBSD port Security: https://www.vuxml.org/freebsd/6a5d15b6-b661-11ea-8015-e09467587c17.html Differential Revision: https://reviews.freebsd.org/D25449 Changes: _U branches/2020Q2/ branches/2020Q2/www/chromium/Makefile branches/2020Q2/www/chromium/distinfo branches/2020Q2/www/chromium/files/patch-base_system_sys__info.cc branches/2020Q2/www/chromium/files/patch-base_system_sys__info__freebsd.cc branches/2020Q2/www/chromium/files/patch-components_sync__device__info_device__info__sync__bridge.cc
While this update brings back sync, now U2F using security keys crashes the browser again, meaning I can no longer sign in to Google, Github or other sites with a security key :(
(In reply to Ulrich Spörlein from comment #8) That's a different issue though, here is the fix: https://source.chromium.org/chromium/chromium/src/+/6ddec2fbc4e0f917b5dc257184089fdc402d849c https://github.com/openbsd/ports/commit/271300ed3a10a5b8063ef7d0cf26ce1860fa34fa