User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.4) Gecko/20100611 Firefox/3.6.4 ( .NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.4) Gecko/20100611 Firefox/3.6.4 ( .NET CLR 3.5.30729) I've read somewhere (Google Groups) that Firefox Sync (formerly Weave) 1.4 is supposed to automatically connect on Login (after a few minutes), since the entry has been dropped from the status bar. However, it does not do so for me. Reproducible: Always Actual Results: Does not auto-connect/-sync on Firefox startup (although security passphrase is being asked). Expected Results: Should auto-connect and auto-sync after Firefox startup. about:sync-log: 2010-06-30 14:33:36 Service.Main INFO Loading Weave 1.4b3 2010-06-30 14:33:36 Engine.Bookmarks DEBUG Engine initialized 2010-06-30 14:33:36 Engine.Forms DEBUG Engine initialized 2010-06-30 14:33:36 Engine.History DEBUG Engine initialized 2010-06-30 14:33:36 Engine.Passwords DEBUG Engine initialized 2010-06-30 14:33:36 Engine.Prefs DEBUG Engine initialized 2010-06-30 14:33:36 Engine.Tabs DEBUG Engine initialized 2010-06-30 14:33:36 Engine.Tabs DEBUG Resetting tabs last sync time 2010-06-30 14:33:37 Service.Main INFO Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.4) Gecko/20100611 Firefox/3.6.4 ( .NET CLR 3.5.30729) 2010-06-30 14:33:37 Service.Util DEBUG Using a fake svc object for @labs.mozilla.com/Weave/Crypto;2 2010-06-30 14:33:37 Service.Main DEBUG Caching URLs under storage user base: https://weave.thequod.de/1.0/daniel/ It's 14:45 now, so it should have auto-connected already. I had it also wait for much longer before.

(In reply to comment #0) > I've read somewhere (Google Groups) that Firefox Sync (formerly Weave) 1.4 is > supposed to automatically connect on Login (after a few minutes), since the > entry has been dropped from the status bar. The autoconnect is not a new feature in 1.4, previous versions autoconnect too (within a few seconds, by the way, not minutes). They don't when you've got a master password set up. > Does not auto-connect/-sync on Firefox startup (although security passphrase is > being asked). Do you mean the master password?

Yes, I have a master password. I'm getting asked about it during startup (probably via the "Read It Later" extension), so Firefox Sync could make use of the opened encryption store, too. Besides, Firefox Sync could just ask the same way as "Read It Later" does during startup, couldn't it?

If autoconnect is enabled, we'll retry again later, once it's actually unlocked. We could force a MP prompt at startup, but the goal is to be as unobtrusive as possible. There's a bug for revisiting this, and perhaps prompting if the master password isn't unlocked after some interval, duping to that.

I'm unduping this: I enter the master password during Firefox startup (probably because of "Read It Later"), and waiting for more than 1 hour (while using the browser), Sync does not connect. Here are some relevant settings: services.sync.lastSync;Thu Jul 01 2010 14:22:38 GMT+0200 services.sync.autoconnect;true services.sync.syncInterval;3600000 services.sync.syncThreshold;500 Here's the log (it's 15:59 now): 2010-07-01 14:55:53 Service.Main INFO Loading Weave 1.4 2010-07-01 14:55:53 Engine.Bookmarks DEBUG Engine initialized 2010-07-01 14:55:53 Engine.Forms DEBUG Engine initialized 2010-07-01 14:55:53 Engine.History DEBUG Engine initialized 2010-07-01 14:55:53 Engine.Passwords DEBUG Engine initialized 2010-07-01 14:55:53 Engine.Prefs DEBUG Engine initialized 2010-07-01 14:55:53 Engine.Tabs DEBUG Engine initialized 2010-07-01 14:55:53 Engine.Tabs DEBUG Resetting tabs last sync time 2010-07-01 14:55:53 Service.Main INFO Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.4) Gecko/20100611 Firefox/3.6.4 ( .NET CLR 3.5.30729) 2010-07-01 14:55:53 Service.Util DEBUG Using a fake svc object for @labs.mozilla.com/Weave/Crypto;2 2010-07-01 14:55:53 Service.Main DEBUG Caching URLs under storage user base: https://weave.thequod.de/1.0/daniel/

How many computers do you use Sync on? If it is only one, then we currently sync once a day.

This doesn't have to do with syncing, this is about automatically logging in (="Connect" in the UI). Sync does that automatically a few *seconds* after starting Firefox, *unless* you Sync was disconnected when Firefox was last quite *or* you have a master password set up. I agree that we should fix that last bit. Sync should prompt for the master password, or at least produce some sort of warning icon along the lines of "btw, I'm not connected, need your master password for that". Either way, that's exactly what bug 543784 is about, so let's discuss this there.

By the way, if you have a master password set up and unlock it during the course of the Firefox session, Sync will eventually autoconnect, too. Perhaps that's what you meant when you said you're unduping this. But since that works just fine with Sync 1.4 (I just tested it again), the bug would still be resolved, just as WORKSFORME ;).

> if you have a master password set up and unlock it during the course of the Firefox session, Sync will eventually autoconnect Not in my case. That's my point. Maybe this is related to the master password getting asked during startup (via another extension)? Can we have some log output regarding this, e.g. when Sync might auto-connect, but then does not, for whatever reason? I'll try with "Read It Later" (or whatever might cause the master password dialog during startup) disabled. (btw: thought I had post a more lenghty comment already, but apparently it got lost?!)

Well, not being asked for the master password during startup already does not fix/work around this: 1. I've made sure that Sync was connected and had synced before closing firefox. 2. After starting Firefox, I've waited about a minute, then went to sf.net which triggered the master password dialog 3. I've entered the password and the password field was filled automatically 4. Sync still does not autoconnect (which should have happened in seconds already) While it may be WORKSFORME for you, it's quite annoying for me. As a workaround, I might add something to vimperatorrc to work around this (like a mapped hotkey which does Connect or give auto-connect a try), but that won't help others, which may have the same bug, of course. Can you add more verbose logging for this - or tell me how I can do so myself?

about:sync-log should show the retry details/timing. It's not immediate, because there's no notification for mp-unlocked. If there were, this would be much better...

> about:sync-log should show the retry details/timing It does not do so for me. On both setups I'm using with Sync (Windows and Linux). Waiting for 1+ hour.

I'm using the minimal server, does that matter?

Just wanted to point to bug 576749#24 - I have found extensions that apparently interfere here: User Agent Switcher and Vimperator. Disabling those makes auto-login work for me, but disabling Vimperator is a no-go.