Closed Bug 561812 Opened 14 years ago Closed 13 years ago

"Unknown error" when trying to connect if no passwords are stored

Categories

(Cloud Services :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 553400

People

(Reporter: zohn.joidberg, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3

I use weave on a PC on which I don't want to store any passwords, but don't mind storing my bookmarks for convenience.
So I set up firefox to always clear everything on close, including passwords.

This leads to 2 annoying problems:
1) My weave account name remains stored.
2) Whenever I want to connect to weave to sync my bookmarks, I get a red "Unknown error" message in the weave preferences tab.

The only way to get around it is to click "Use a different account" with a scary message about "losing all your data".

I suppose the right thing to do might be to use my own profile with a master password and create a special launcher for it or always ask for profile selection (I don't know how to do that yet, but I suppose it is possible).

But I really don't see why it doesn't just:
1) Ask for my pasword+passphrase
or
2) Forget my account name, the same way it forgets all stored login names (when clearing passwords)


Reproducible: Always

Steps to Reproduce:
1.Install weave
2.Set Firefox to clear everything including passwords on close
3.Restart firefox
4.Try to connect to weave

Actual Results:  
Red "Unknown error" message


Expected Results:  
1) Ask for my pasword+passphrase
or
2) Forget my account name, the same way it forgets all stored login names (when clearing passwords). Then ask for login+password when trying to connect.
Component: Needs Triage → General
QA Contact: needstriage → general
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.