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

Issue 616097 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jun 2016
Cc:
mastiz@chromium.org
█ tschumann@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Bookmark folder name changes not syncing

Reported by har...@gmail.com, May 31 2016 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.63 Safari/537.36

Steps to reproduce the problem:
1. Sign in to chrome on windows
2. Rename a bookmark folder in the bookmarks bar
3. Sign in to chrome on linux

What is the expected behavior?
Bookmark folder name change is changed on linux.

What went wrong?
Bookmark folder name is not changed.

Did this work before? N/A 

Chrome version: 51.0.2704.63  Channel: stable
OS Version: Ubuntu 14.04 amd64
Flash Version: Shockwave Flash 21.0 r0

Bookmark entries do get synced immediately. 
I always select just bookmarks and passwords to sync at sign in.
It probably reproduces on windows too, not just linux.
I allowed days for the sync to happen, enabled developer mode and clicked on "Update all extensions now" to trigger the sync, signed out and back in, but no luck so far.

Comment 1 by pav...@chromium.org, Jun 1 2016

Labels: Needs-Feedback
harjoc@:  could you try to repro it again? Here are the steps:
- sign in to Chrome on both Windows and Linux clients. Make sure they are connected to network.
- Rename bookmark folder on Windows client, wait for 15 seconds.
- If folder name doesn't get updated on Linux could you collect sync status from Windows machine? Open about:sync in new tab, click on "Dump status" and post contents of the text box here.

Comment 2 by pav...@chromium.org, Jun 1 2016 

I tried to reproduce this bug several times today. 
One time, after renaming folder, entry was committed to server successfully (about:sync on sending side showed CommitRequest with successful response). The other client didn't receive invalidation about this change for a few minutes (about:invalidations and about:gcm-internals didn't show any incoming messages, GCM connection state was "CONNECTED").

This hints at potential issue with delivering invalidation on server side.

I wasn't able to reproduce this issue reliably though.

Comment 3 by har...@gmail.com, Jun 2 2016 

Apparently just one folder name was outdated on that Linux machine. I renamed it now on another Windows machine, and the change synced to Linux in a few seconds. You can close the issue if there are no other reports, I'll open again if it reproduces. Thanks.

Comment 4 by pav...@chromium.org, Jun 2 2016

Status: WontFix (was: Unconfirmed)
Closing as "not repro". Feel free to reopen if it happens again.

The issue I saw in #2 was caused by short server outage yesterday.
►

Sign in to add a comment