479570 - Weave logins on startup fail initially if auto-detection of proxy settings is enabled

Status: RESOLVED WORKSFORME

(Firefox :: Sync, defect, P3)

Description

[Adam Bishop]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-GB; rv:1.9.1b2) Gecko/20081201 Firefox/3.1b2
Build Identifier: 2.9.102

Using Firefox 3.1b2 + OS X 10.5.6, weave requires me to log in 3 times.
The first time (automatic login) fails with a /!\ message in the statusbar:

Weave Encountered an Error While signing you in: % Please try again.

The second time (manual login) weave will claim that the username/password is incorrect.

The third time (manual login), it will log me in.

This issue happens every time the browser is closed.

This issue has existed since at least 0.2.99, possibly longer.

-------------------------------------------------------------------------------

2009-02-21 08:34:16	Service.Main	INFO	Weave 0.2.102 initializing
2009-02-21 08:34:16	Service.Main	INFO	Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-GB; rv:1.9.1b2) Gecko/20081201 Firefox/3.1b2
2009-02-21 08:34:16	Service.Main	DEBUG	Event: weave:service:login:start
2009-02-21 08:34:16	Chrome.Window	INFO	Logging in...
2009-02-21 08:34:16	Service.Main	DEBUG	Logging in user themysteriousx
2009-02-21 08:34:16	Service.Main	DEBUG	Event: weave:service:verify-login:start
2009-02-21 08:34:16	Service.Main	DEBUG	Verifying login for user themysteriousx
2009-02-21 08:34:16	Service.Main	DEBUG	Finding cluster for user themysteriousx
2009-02-21 08:34:17	Service.Main	DEBUG	Event: weave:service:verify-login:error
2009-02-21 08:34:17	Service.Main	DEBUG	Caught exception: Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIHttpChannel.responseStatus] (JS frame :: file:///Users/adam/Library/Application%20Support/Firefox/Profiles/05mghies.default/extensions/%7B340c2bbc-ce74-4362-90b5-7c26312808ef%7D/modules/service.js :: WeaveSvc__findCluster :: line 446)
2009-02-21 08:34:17	Service.Main	DEBUG	
Original exception: Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIHttpChannel.responseStatus] (JS frame :: file:///Users/adam/Library/Application%20Support/Firefox/Profiles/05mghies.default/extensions/%7B340c2bbc-ce74-4362-90b5-7c26312808ef%7D/modules/service.js :: WeaveSvc__findCluster :: line 446)
Async stack trace:
module:wrap.js:164 :: WeaveCatchAllWrapper
module:service.js:479 :: WeaveSvc_verifyLogin
module:service.js:530 :: WeaveSvc__login
module:wrap.js:95 :: WeaveNotifyWrapper
module:wrap.js:134 :: WeaveLocalLockWrapper
module:wrap.js:164 :: WeaveCatchAllWrapper
module:service.js:543 :: WeaveSvc_login
module:service.js:354 :: WeaveSvc__onStartup
module:service.js:361 :: WeaveSvc_onStartup
module:Weave.js:61 :: BSS__observe
<file:unknown>
module:nsSessionStore.js:498 :: sss_onLoad
module:nsSessionStore.js:269 :: sss_init
<file:unknown>
chrome://browser/content/browser.js:1173 :: delayedStartup
Last callback created at module:wrap.js:94 :: WeaveNotifyWrapper
2009-02-21 08:34:17	Service.Main	CONFIG	Weave scheduler disabled
2009-02-21 08:34:17	Service.Main	DEBUG	Event: weave:service:login:error
2009-02-21 08:34:17	Chrome.Window	INFO	Login Error
2009-02-21 08:34:17	Service.Main	DEBUG	Caught exception: Login failed
2009-02-21 08:34:17	Service.Main	DEBUG	
Original exception: Login failed
Async stack trace:
module:wrap.js:164 :: WeaveCatchAllWrapper
module:service.js:543 :: WeaveSvc_login
module:service.js:354 :: WeaveSvc__onStartup
module:service.js:361 :: WeaveSvc_onStartup
module:Weave.js:61 :: BSS__observe
<file:unknown>
module:nsSessionStore.js:498 :: sss_onLoad
module:nsSessionStore.js:269 :: sss_init
<file:unknown>
chrome://browser/content/browser.js:1173 :: delayedStartup
Last callback created at module:wrap.js:133 :: WeaveLocalLockWrapper
2009-02-21 08:34:19	HistoryTracker	TRACE	onVisit: http://en-gb.start2.mozilla.com/firefox?client=firefox-a&rls=org.mozilla:en-GB:official
2009-02-21 08:34:19	HistoryTracker	DEBUG	Adding changed ID 592a7520-3747-a540-8d72-7ab0c8c4527e
2009-02-21 08:34:19	HistoryTracker	DEBUG	Saving changed IDs to disk
2009-02-21 08:34:19	HistoryTracker	TRACE	onVisit: http://en-gb.start2.mozilla.com/firefox?client=firefox-a&rls=org.mozilla:en-GB:official
2009-02-21 08:34:19	HistoryTracker	TRACE	onVisit: http://www.google.com/firefox?client=firefox-a&rls=org.mozilla:en-GB:official
2009-02-21 08:34:20	HistoryTracker	TRACE	onVisit: http://www.google.co.uk/firefox?client=firefox-a&rls=org.mozilla:en-GB:official
2009-02-21 08:34:20	Chrome.Login	TRACE	Sync login window opened
2009-02-21 08:34:22	Service.Util	TRACE	Setting 'Mozilla Services Password' password for user themysteriousx
2009-02-21 08:34:22	Service.Util	TRACE	Setting 'Mozilla Services Encryption Passphrase' password for user themysteriousx
2009-02-21 08:34:22	Service.Main	DEBUG	Event: weave:service:login:start
2009-02-21 08:34:22	Chrome.Window	INFO	Logging in...
2009-02-21 08:34:22	Service.Util	TRACE	Setting 'Mozilla Services Password' password for user themysteriousx
2009-02-21 08:34:22	Service.Util	TRACE	Setting 'Mozilla Services Encryption Passphrase' password for user themysteriousx
2009-02-21 08:34:22	Service.Main	DEBUG	Logging in user themysteriousx
2009-02-21 08:34:22	Service.Main	DEBUG	Event: weave:service:verify-login:start
2009-02-21 08:34:22	Service.Main	DEBUG	Verifying login for user themysteriousx
2009-02-21 08:34:22	Service.Main	DEBUG	Finding cluster for user themysteriousx
2009-02-21 08:34:22	Service.Main	DEBUG	Event: weave:service:verify-login:error
2009-02-21 08:34:22	Service.Main	DEBUG	Caught exception: Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIHttpChannel.responseStatus] (JS frame :: file:///Users/adam/Library/Application%20Support/Firefox/Profiles/05mghies.default/extensions/%7B340c2bbc-ce74-4362-90b5-7c26312808ef%7D/modules/service.js :: WeaveSvc__findCluster :: line 446)
2009-02-21 08:34:22	Service.Main	DEBUG	
Original exception: Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIHttpChannel.responseStatus] (JS frame :: file:///Users/adam/Library/Application%20Support/Firefox/Profiles/05mghies.default/extensions/%7B340c2bbc-ce74-4362-90b5-7c26312808ef%7D/modules/service.js :: WeaveSvc__findCluster :: line 446)
Async stack trace:
module:wrap.js:164 :: WeaveCatchAllWrapper
module:service.js:479 :: WeaveSvc_verifyLogin
module:service.js:530 :: WeaveSvc__login
module:wrap.js:95 :: WeaveNotifyWrapper
module:wrap.js:134 :: WeaveLocalLockWrapper
module:wrap.js:164 :: WeaveCatchAllWrapper
module:service.js:543 :: WeaveSvc_login
chrome://weave/content/login.js:146 :: Login_doOK
chrome://global/content/bindings/dialog.xml:345 :: anonymous
chrome://global/content/bindings/dialog.xml:346 :: _fireButtonEvent
chrome://global/content/bindings/dialog.xml:320 :: _doButtonCommand
chrome://global/content/bindings/dialog.xml:309 :: _handleButtonCommand
Last callback created at module:wrap.js:94 :: WeaveNotifyWrapper
2009-02-21 08:34:22	Service.Main	CONFIG	Weave scheduler disabled
2009-02-21 08:34:22	Service.Main	DEBUG	Event: weave:service:login:error
2009-02-21 08:34:22	Chrome.Window	INFO	Login Error
2009-02-21 08:34:23	Service.Main	DEBUG	Caught exception: Login failed
2009-02-21 08:34:23	Service.Main	DEBUG	
Original exception: Login failed
Async stack trace:
module:wrap.js:164 :: WeaveCatchAllWrapper
module:service.js:543 :: WeaveSvc_login
chrome://weave/content/login.js:146 :: Login_doOK
chrome://global/content/bindings/dialog.xml:345 :: anonymous
chrome://global/content/bindings/dialog.xml:346 :: _fireButtonEvent
chrome://global/content/bindings/dialog.xml:320 :: _doButtonCommand
chrome://global/content/bindings/dialog.xml:309 :: _handleButtonCommand
Last callback created at module:wrap.js:133 :: WeaveLocalLockWrapper
2009-02-21 08:34:23	Service.Util	TRACE	Setting 'Mozilla Services Password' password for user themysteriousx
2009-02-21 08:34:23	Service.Util	TRACE	Setting 'Mozilla Services Encryption Passphrase' password for user themysteriousx
2009-02-21 08:34:23	Service.Main	DEBUG	Event: weave:service:login:start
2009-02-21 08:34:23	Chrome.Window	INFO	Logging in...
2009-02-21 08:34:23	Service.Util	TRACE	Setting 'Mozilla Services Password' password for user themysteriousx
2009-02-21 08:34:23	Service.Util	TRACE	Setting 'Mozilla Services Encryption Passphrase' password for user themysteriousx
2009-02-21 08:34:23	Service.Main	DEBUG	Logging in user themysteriousx
2009-02-21 08:34:23	Service.Main	DEBUG	Event: weave:service:verify-login:start
2009-02-21 08:34:23	Service.Main	DEBUG	Verifying login for user themysteriousx
2009-02-21 08:34:23	Service.Main	DEBUG	Finding cluster for user themysteriousx
2009-02-21 08:34:24	Net.Resource	DEBUG	GET request for https://auth.services.mozilla.com/0.3/api/register/chknode/themysteriousx
2009-02-21 08:34:24	Net.Resource	DEBUG	GET request successful (200)
2009-02-21 08:34:25	Net.Resource	DEBUG	GET request for https://sj-weave01.services.mozilla.com/0.3/user/themysteriousx
2009-02-21 08:34:25	Net.Resource	DEBUG	GET request successful (200)
2009-02-21 08:34:25	Service.Main	DEBUG	Event: weave:service:verify-login:success
2009-02-21 08:34:25	Service.Main	CONFIG	Weave scheduler enabled
2009-02-21 08:34:25	Service.Main	DEBUG	Event: weave:service:login:success
2009-02-21 08:34:25	Chrome.Window	INFO	Login successful
2009-02-21 08:34:26	Chrome.Login	TRACE	Sync login window closed


Reproducible: Always

Steps to Reproduce:
1. Close Firefox
2. Open Firefox (weave will fail to log in)
3. Sign in manually (weave will fail to log in)
4. Sign in manually again (weave will log in)


Expected Results:  
Weave should automatically log in when the browser is opened if requested, or on demand with as much reliability as possible.

Comment 1

[Adam Bishop]

Attachment: Weave log

Weave log, as bugzilla has butchered the formatting.

Comment 2

[Dan Mills [:thunder]]

Interesting... I see it's returning NS_ERROR_NOT_AVAILABLE, perhaps your internet connection is not fully available when you are starting up the browser?

Comment 3

[Adam Bishop]

Internet connection is definitely available, but I have been able to track down an indirect cause thanks to your comment.

When FX has its proxy settings to auto-detect (ask the OS), the issue occurs (on my home network there is no proxy, but I have a separate network profile for work which does have one, so I leave it on auto-detect).
When set to "No Proxy" weave signs in as normal.

That would explain the automatic failure (Weave trying to access the network before FX has asked the OS for proxy data), but not the second failure (the home page has loaded at this point, so FX has finished setting itself up).

Comment 4

[Adam Bishop]

Just confirmed the issue on Windows too - 3x sign in when set to autodetect, works fine when set to no proxy.

Comment 5

[Dan Mills [:thunder]]

Aha, that makes sense.  Not sure what the fix is, maybe we just need to wait until the proxy config settles before trying any connections.

Comment 6

[laurent]

I can confirm this bug on Ubuntu 8.10 (Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.9.1b2) Gecko/20081201 Firefox/3.1b2). My proxy is configured to use system's proxy config and my internet access needs to go through the proxy. When my credentials for the proxy have been entered (because I visited a page) and saved, I can try again to sign in weave and it works.

Comment 10

[laurent]

Hum... I still have the bug when my proxy settings is set to manual. Should I open a new bug ?

Comment 11

[Mike Connor [:mconnor]]

If we're failing because you're not signed into your properly-configured proxy, that would be a separate bug, IMO.

Comment 12

[Mike Connor [:mconnor]]

This seems to be working in 0.7.  There's a few different things that could have impacted this, but in any case, this is WORKSFORME now, so resolving.

Adam, if you can still reproduce with Weave 0.7 or higher, please reopen this bug.