New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 908480 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 28
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

chrome bookmarks are not being picked up by sync on Ubuntu 18.04

Reported by david.co...@gmail.com, Nov 26

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36

Steps to reproduce the problem:
Run ubuntu 18.04 and install chrome. Log in yet no bookmarks.

What is the expected behavior?
Bookmarks exist 

What went wrong?
No bookmarks. They are empty.

Did this work before? N/A 

Chrome version: 70.0.3538.110  Channel: stable
OS Version: 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Flash Version:
 
A full log-out and clearing everything seems to have fixed this. Not quite sure what the issue was and is a bit hard to reproduce. Probably best to close this for now.
Labels: Needs-Triage-M70
Cc: phanindra.mandapaka@chromium.org
Labels: TE-NeedsTriageFromMTV Triaged-ET
Thanks for filing the issue...

Unable to reproduce the issue on reported chrome version 70.0.3538.110 using Mac 17.10. Attaching screenshot for reference.
Steps: 
------
1. Launched reported chrome 
2. Bookmarked some site and synced to chrome 
3. Opened new profile and synced with same account 
As we have observed all the bookmarks are synced and as this issue was reported on Ubuntu 18.10. Hence adding 'TE-NeedsTriageFromMTV' label and requesting the team to look into the issue and help in further triaging.

Thanks...!


Thanks.!
908480.png
60.0 KB View Download
Labels: Sync-Triaged
Status: WontFix (was: Unconfirmed)
Thank you for reporting this bug.

It will be hard to debug it without repro steps or more information such as 
chrome://sync-internals and chrome://signin-internals, but it's too late now to get such information after the issue has been fixed.

I will close this bug and feel free to reopen it again if needed.


Sign in to add a comment