1639625 - Sync logs state that addon, address, form, prefs, history sync disabled via preference, but is not disabled

Status: RESOLVED INCOMPLETE

(Firefox :: Sync, defect)

Description

[Asif Youssuff]

Created a fresh profile of Firefox last night and was surprised to not see my add-ons populate as usually occurs in new profiles.

Looked in my sync logs and saw lines like:

1589992786861	Sync.Doctor	INFO	Skipping check of prefs - disabled via preferences
1589992786861	Sync.Doctor	INFO	Skipping validation of passwords: too recent since last validation attempt
1589992786861	Sync.Doctor	INFO	Skipping check of tabs - disabled via preferences
1589992786861	Sync.Doctor	INFO	Skipping validation of bookmarks: too recent since last validation attempt
1589992786861	Sync.Doctor	INFO	Skipping check of addons - disabled via preferences
1589992786861	Sync.Doctor	INFO	Skipping check of addresses - disabled via preferences
1589992786861	Sync.Doctor	INFO	Skipping check of forms - disabled via preferences
1589992786861	Sync.Doctor	INFO	Skipping check of history - disabled via preferences

which is not true.

Why is this?

Comment 1

[Asif Youssuff]

Attachment: error-sync-1589992786888.txt

Comment 2

[Asif Youssuff]

Attachment: about:support

Comment 3

[Lina Butler (ex-Mozilla)]

Hi! There are a few things going on there.

First, sorry for the confusing messages—the "disabled via preferences" line means it's skipping validation and repair (that's what Sync.Doctor does) for those engines, because validation is disabled via preferences...not the engine itself.

I'm not sure what's going on with add-ons; it does look like at least ClearURLs gets uploaded—is it not installed on your fresh profile?

1589992782029 Sync.Engine.Addons.Tracker DEBUG changeListener invoked: 1 {74145f27-f039-47ce-a470-a662b129930a}
1589992782029 Sync.AddonsReconciler DEBUG Rectifying state for addon ClearURLs (version=1.17.0, id={74145f27-f039-47ce-a470-a662b129930a})
1589992782029 Sync.AddonsReconciler DEBUG Adding change because add-on not present locally: {74145f27-f039-47ce-a470-a662b129930a}
1589992782029 Sync.AddonsReconciler INFO Change recorded for {74145f27-f039-47ce-a470-a662b129930a}
1589992786187 Sync.Engine.Addons DEBUG Adding changed add-on from changes log: {74145f27-f039-47ce-a470-a662b129930a}
1589992786187 Sync.Engine.Addons INFO 1 outgoing items pre-reconciliation
1589992786192 Sync.Engine.Addons INFO Posting 1 records of 479 bytes with batch=true

This error from tabs, on the other hand, looks like a regression from bug 1636365!

1589992785906 Sync.ErrorHandler DEBUG tabs failed: TypeError: Can't add changed ID to this tracker(resource://services-sync/engines.js:120:11) JS Stack trace:

Comment 4

[Lina Butler (ex-Mozilla)]

Oops, I didn't mean to close this!

Comment 5

[Asif Youssuff]

I'm not sure what's going on with add-ons; it does look like at least ClearURLs gets uploaded—is it not installed on your fresh profile?

I installed this manually.

I just rebooted into my Windows install and did another sync and rebooted back into Linux and synced again (the log is from my Linux install) and now my add-ons are appearing.

Not sure what changed. I can provide logs from both installs if you like since I opened the bug.

Comment 6

[Mark Hammond [:markh] [:mhammond]]

Not sure what changed. I can provide logs from both installs if you like since I opened the bug.

If you have full "success" logs at trace level (eg, via installing the about:sync addon), then the logs from both devices might help us decipher what caused the syncing of your addons to be delayed - otherwise, I doubt it will be possible to tell given things seem to be working now.

Comment 7

[BugBot [:suhaib / :marco]]

The severity field is not set for this bug.
:markh, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 8

[Ryan Kelly [:rfkelly]]

Thanks again for reporting this issue, but we are unable to determine the cause of the problem without the requested information. If you are able to provide this information, please just add a comment in this bug with that information and we'll get back to you as soon as we can, but in the meantime we are closing this bug so we can focus on the issues which we can address.