Closed
Bug 445286
Opened 17 years ago
Closed 16 years ago
"save password"-button don't do anything
Categories
(Toolkit :: Password Manager, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: alex, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9) Gecko/2008052906 Firefox/3.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9) Gecko/2008052906 Firefox/3.0
when i enter a password on any site the horizontal "safe password"-bar appears on the upper screen. the safe-button does not do anything. i can click it multiple times. the bar does not hide.
all other buttons "never for this site" or "not now" or the close-button working.
i reinstalled Firefox twice but the bug does not disappear
Reproducible: Always
Steps to Reproduce:
1. enter a password on any site
2. click on "safe password"
Actual Results:
nothing happens. the password bar didn't disappear
Expected Results:
the password bar should disappear. passwords not safed
Comment 1•16 years ago
|
||
Do you see anything in the Error Console when doing this?
If not, please attach some log output here per http://wiki.mozilla.org/Firefox:Password_Manager_Debugging
Summary: "safe password"-button don't do anything → "save password"-button don't do anything
Fehler: [Exception... "'Couldn't write to file, login not added.' when calling method: [nsILoginManagerStorage::addLogin]" nsresult: "0x8057001e (NS_ERROR_XPC_JS_THREW_STRING)" location: "JS frame :: file:///C:/Programme/Mozilla%20Firefox/components/nsLoginManager.js :: anonymous :: line 388" data: no]
Quelldatei: file:///C:/Programme/Mozilla%20Firefox/components/nsLoginManager.js
Zeile: 388
Assignee | ||
Updated•16 years ago
|
Product: Firefox → Toolkit
Comment 3•16 years ago
|
||
Is there any debug output before that? Does this only happen after performing a "Clear Private Data"?
sorry, I reinstalled my whole system. I don't have the bug any more
Updated•16 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•