Something regressed with bug 557590 2010-06-02 15:09:29 Service.Main DEBUG checkSetup: no username set 2010-06-02 15:09:49 Service.Main DEBUG Exception: aborting login, client not configured No traceback available
Does this affect all 1.3 users? As in, if I am running 1.3, can I not set up a 2nd computer?
Nah. bug 557590 landed after 1.3.
Mea culpa. I was a bit overzealous with the refactoring and neglected that case :/. I'll prepare a patch.
Assignee: nobody → philipp
Created attachment 449250 [details] [diff] [review] Fix + test v1 Reintroduces an 'else' clause the refactoring in bug 557590 mistakenly threw out.
Created attachment 449260 [details] [diff] [review] Fix + test v1.1 Improve teardown (clean up preferences).
Comment on attachment 449260 [details] [diff] [review] Fix + test v1.1 >+ // We need a non-empty passphrase for login to work. Even the >+ // setup wizard just sets this to 'foo' if there isn't a >+ // passphrase yet. >+ Weave.Service.passphrase = "foo"; Can you file a bug to make sure this is investigated and made sure it's ok?
Attachment #449260 - Flags: review?(edilee) → review+
http://hg.mozilla.org/labs/weave/rev/710dec717f8d Fix a regression introduced with the status.js refactoring (bug 557590).
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → 1.4
You need to log in before you can comment on or make changes to this bug.