Join the Mozilla’s Test Days event from Dec 2–8 to test the new Firefox address bar on Firefox Beta 134 and get a chance to win Mozilla swag vouchers! 🎁

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox Sync synchronizes Windows 10 but not on dual boot Linux Mint 17.3?

  • 5 replies
  • 4 have this problem
  • 19 views
  • Last reply by jossiloumar

more options

Hey there,

I use Firefox Sync to sync almost everything from my PC/Laptop with Windows 10 to my Android phone - without problems. Since I use Sync with email & password, I think I already use the newer version of Sync.

A few days ago I installed Linux Mint 17.3 Cinnamon 64-bit alongside Windows 10 on the same PC/Laptop. To have access my Firefox data in Linux Mint, I logged in to Firefox Sync with my email and password - same as I use on Windows 10 and my Android phone.

Here the thing: Firefox Sync on Linux Mint is set up, but it's not synchronizing anything... Even if I click the sync button next to my name in the dropdown menu.

Any suggestions?

Thanks in advance!

Hey there, I use Firefox Sync to sync almost everything from my PC/Laptop with Windows 10 to my Android phone - without problems. Since I use Sync with email & password, I think I already use the newer version of Sync. A few days ago I installed Linux Mint 17.3 Cinnamon 64-bit alongside Windows 10 on the same PC/Laptop. To have access my Firefox data in Linux Mint, I logged in to Firefox Sync with my email and password - same as I use on Windows 10 and my Android phone. Here the thing: Firefox Sync on Linux Mint is set up, but it's not synchronizing anything... Even if I click the sync button next to my name in the dropdown menu. Any suggestions? Thanks in advance!

Modified by jossiloumar

Chosen solution

thanks, then it's likely that you are experiencing a bug with the unitymedia ds-light network: https://bugzilla.mozilla.org/show_bug.cgi?id=1118958 - for a workaround see comment #19 there.

Read this answer in context 👍 1

All Replies (5)

more options

hi, which isp are you using?

more options

Hi philipp, I'm on cable ISP called Unitymedia (in Germany ;) )

more options

How long did you let the initial Sync run on that new installation? Maybe it needs more time.

Also, you can check about:sync-log (typed in the URL bar) to see if there are any sync error reports saved.

If so copy & paste the report to - http://pastebin.mozilla.org/ - and post the resulting URL to this forum. Make sure you select "a month" for retention of that "paste", as "a day" usually isn't long enough especially leading into a weekend.

more options

Chosen Solution

thanks, then it's likely that you are experiencing a bug with the unitymedia ds-light network: https://bugzilla.mozilla.org/show_bug.cgi?id=1118958 - for a workaround see comment #19 there.

more options
the-edmeister said
How long did you let the initial Sync run on that new installation? Maybe it needs more time. Also, you can check about:sync-log (typed in the URL bar) to see if there are any sync error reports saved.

Hi the-edmeister, thanks for your answer. Of course I gave Sync enough time to do the initial sync. I think 5 days (more or less without turning my Laptop off) should be more than enough ;)

I looked at about:sync-log (which I didn't know before your post) and there are several error logs since... 5 days :P I won't post a log now, because philipp gave a great hint...


philipp said
for a workaround see comment #19 there

Since I don't know what to replace e.g. "what:ever/128" to, I read some comments below on that page and [comment 27] said to set "sysctl -w net.ipv4.tcp_mtu_probing=1" [in terminal], which worked flawlessly and after a Firefox restart, Sync started immediately. Even if I don't really know what that setting does... xD

Now I have all my bookmarks, passwords etc. synchronized.

Thanks to both of you!


If anyone wants me to provide a sync error log, when net.ipv4.tcp_mtu_probing was set to 0, I will post it to try to help fixing that bug(? If it can be fixed).