Closed Bug 453386 Opened 17 years ago Closed 16 years ago

Bogus error: "Invalid username and/or password"

Categories

(Cloud Services :: General, defect)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: johnfrombluff, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.0.1) Gecko/2008070206 Firefox/3.0.1 Build Identifier: 0.2.6 Sometimes Weave can sign in automatically, sometimes it can't. Sometimes I can sign in manually, sometimes I can't. But in all cases I get the error message "Invalid username and/or password". This cannot be true! I have changed neither and I know they are correct because sometimes Weave works. Reproducible: Sometimes Steps to Reproduce: 1. Try to sign in to Weave 2. Use the previously remembered username and password 3. Observe bogus error message, and weep with frustration Actual Results: Bogus error message Expected Results: An error message that GIVES ME A CLUE what's going on, and how I could fix it (or not)
I also get this error - for me it produces the following error in the logs: 2008-09-10 22:43:00 Chrome.Window INFO Logging in... 2008-09-10 22:43:00 Chrome.Window INFO User string: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.0.1) Gecko/2008072820 Firefox/3.0.1 2008-09-10 22:43:00 Chrome.Window INFO Weave version: 0.2.6 2008-09-10 22:43:00 Service.Main INFO Making sure server is initialized... 2008-09-10 22:43:00 Async.Generator ERROR Exception: Request already in progress I think this may happen because Firefox doesn't close properly, presumably while doing the closing Synch (using Ubuntu - on my Mac it works fine).
Can you re-test with 0.2.99? A lot of the networking and login core has been rewritten since 0.2.6.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
Component: Weave → General
Product: Mozilla Labs → Weave
Target Milestone: -- → ---
Component: Weave → General
Product: Mozilla Labs → Weave
Target Milestone: -- → ---
QA Contact: weave → general
You need to log in before you can comment on or make changes to this bug.