Closed Bug 483045 Opened 15 years ago Closed 15 years ago

Weave cannot login at FF start - but manual login works fine

Categories

(Cloud Services :: General, defect, P2)

x86
Windows Vista
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 479570

People

(Reporter: stefan, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3 (.NET CLR 3.5.30729)
Build Identifier: Weave 0.2.112

Log Message:

2009-03-10 18:25:51 TabTracker TRACE Spotted window open/close

2009-03-10 18:25:41 Service.Main DEBUG

2009-03-10 18:25:41 Service.Main DEBUG Caught exception: Login failed

2009-03-10 18:25:41 Window INFO Login Error

2009-03-10 18:25:41 Service.Main DEBUG Event: weave:service:login:error

2009-03-10 18:25:41 Service.Main CONFIG Weave scheduler disabled

2009-03-10 18:25:41 Service.Main DEBUG

2009-03-10 18:25:41 Service.Main DEBUG Caught exception: Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIHttpChannel.responseStatus] (JS frame :: file:///C:/Users/stefan/AppData/Roaming/Mozilla/Firefox/Profiles/hy6ws7nm.default/extensions/%7B340c2bbc-ce74-4362-90b5-7c26312808ef%7D/modules/service.js :: WeaveSvc__findCluster :: line 452)

2009-03-10 18:25:41 Service.Main DEBUG Event: weave:service:verify-login:error

2009-03-10 18:25:40 Service.Main DEBUG Finding cluster for user spriebe

2009-03-10 18:25:40 Service.Main DEBUG Verifying login for user spriebe

2009-03-10 18:25:40 Service.Main DEBUG Event: weave:service:verify-login:start

2009-03-10 18:25:40 Service.Main DEBUG Logging in user spriebe

2009-03-10 18:25:40 Window INFO Logging in...

2009-03-10 18:25:40 Service.Main DEBUG Event: weave:service:login:start

2009-03-10 18:25:40 Service.Main INFO Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3 (.NET CLR 3.5.30729)

2009-03-10 18:25:40 Service.Main INFO Weave 0.2.111 initializing 

Reproducible: Always

Steps to Reproduce:
1. start FF :-) but login doesn't work

Actual Results:  
got NS error sign in doesn't work

Expected Results:  
sign in should work

it works if i change service.js

from:
let res = new Resource(this.baseURL + "api/register/chknode/" + username);
try {
yield res.get(self.cb);
} catch (e) { /* we check status below */ }


to:
let res = new Resource(this.baseURL + "api/register/chknode/" + username);
try {
yield res.get(self.cb);
} catch (e) {

try {
yield res.get(self.cb);
} catch (e) { /* we check status below */ }

}
Blocks: 468694
Priority: -- → P2
Target Milestone: -- → 0.3
Could this be caused by an older weave installation? It is also the only client where i have a "Sync Now..." button directly in the context menu (bottom right corne in FF).
I don't see how an old Weave installation could have this effect.
it was just an idea :-)
got the same problem, see this log:

2009-03-24 20:10:16	Window               INFO	Login Error
2009-03-24 20:05:32	Service.Main         INFO	Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3 (.NET CLR 3.5.30729)

2009-03-24 20:05:32	Service.Main         INFO	Weave 0.2.117 initializing

2009-03-24 20:10:16	Service.Main         DEBUG	Event: weave:service:login:error
2009-03-24 20:10:16	Service.Main         DEBUG	
2009-03-24 20:10:16	Service.Main         DEBUG	Caught exception: Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIHttpChannel.responseStatus] (JS frame :: file:///.../modules/service.js :: WeaveSvc__findCluster :: line 394)
2009-03-24 20:10:16	Service.Main         DEBUG	Event: weave:service:verify-login:error

solved it switching from preferences > advanced > network > settings > FROM automatic proxy detection TO no proxy. The error no longer happens.
oh thanks this fix the problem for me too
But i think this must also be fixed by weave... so that automatic proxy works too.
Target Milestone: 0.3 → 0.4
No longer blocks: 468694
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Component: Weave → General
Product: Mozilla Labs → Weave
QA Contact: weave → general
You need to log in before you can comment on or make changes to this bug.