439977 - Password manager disappeared with logins stored

Status: RESOLVED DUPLICATE of bug 435531

(Toolkit :: Password Manager, defect)

Description

[Marcelo]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; pt-BR; rv:1.9) Gecko/2008052906 Firefox/3.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; pt-BR; rv:1.9) Gecko/2008052906 Firefox/3.0

Hi, I have some accounts stored in firefox to login in gmail (around 10). Some of these accounts just password field remian stored, username just disapear (blank username).
Anothers sites like http://www.sky.com.br/MinhaConta/Home/Default.aspx username and password disapear.
Sorry for my bad english...

Reproducible: Always

Steps to Reproduce:
1. Open firefox, and insert master password
2. Click in login cells from gmail.com
3. Some usersnames are missing
4. Some sites username and passwords are missing
Actual Results:  
some usersnames disapears while I try login in gmail and some sites both disapear (username+password).

Expected Results:  
Lists stored usernames and passwords to login in sites.

Comment 1

[Justin Dolske [:Dolske]]

Do are the logins/passwords you expect shown in Tools -> Options -> Security -> Saved Passwords?

Also, please attach some debug logs from http://wiki.mozilla.org/Firefox:Password_Manager_Debugging

Comment 2

[Marcelo]

Hi Justin, thank you for reply.
There is console output.
Login Manager: AutoCompleteSearch invoked. Search is: 
Login Manager: Creating new autocomplete search result.
Login Manager: Searching for logins matching host: https://www.google.com, formSubmitURL: https://www.google.com, httpRealm: null
Login Manager: 11 autocomplete logins avail.
Login Manager: domEventListener: got event DOMAutoComplete
Login Manager: fillPassword autocomplete username: 
Login Manager: Searching for logins matching host: https://www.google.com, formSubmitURL: https://www.google.com, httpRealm: null
Login Manager: Found a matching login, filling in password.
Login Manager: domEventListener: got event blur
Login Manager: observer notified for form submission.
Login Manager: Checking if logins to https://www.google.com can be saved.
Login Manager: Caught error in onFormSubmit: [Exception... "Not enough arguments [nsILoginInfo.matches]"  nsresult: "0x80570001 (NS_ERROR_XPC_NOT_ENOUGH_ARGS)"  location: "JS frame :: file:///C:/Arquivos%20de%20programas/Mozilla%20Firefox/components/nsLoginManager.js :: anonymous :: line 842"  data: no]
Login Manager: onStateChange accepted: req = https://www.google.com/accounts/ServiceLoginAuth?service=mail, flags = 0x30004
Alerta: Seletor esperado.  Regra ignorada devido a seletor incorreto.
Arquivo-fonte: https://www.google.com/accounts/ServiceLoginAuth?service=mail
Linha: 26
Alerta: Fim de arquivo não esperado ao pesquisar por } de fechamento de regra inválida.
Arquivo-fonte: https://www.google.com/accounts/ServiceLoginAuth?service=mail
Linha: 27
Alerta: Seletor esperado.  Regra ignorada devido a seletor incorreto.
Arquivo-fonte: https://www.google.com/accounts/ServiceLoginAuth?service=mail
Linha: 190
Alerta: Fim de arquivo não esperado ao pesquisar por } de fechamento de regra inválida.
Arquivo-fonte: https://www.google.com/accounts/ServiceLoginAuth?service=mail
Linha: 191
Login Manager: domEventListener: got event DOMContentLoaded
Login Manager: Counting logins matching host: https://www.google.com, formSubmitURL: , httpRealm: null
Login Manager: fillDocument processing 2 forms on https://www.google.com/accounts/ServiceLoginAuth?service=mail
Login Manager: Searching for logins matching host: https://www.google.com, formSubmitURL: https://www.google.com, httpRealm: null
Login Manager: form[0]: found 11 matching logins.
Login Manager: attaching autocomplete stuff
Login Manager: Multiple logins for form, so not filling any.
Login Manager: (form ignored -- no password fields.)
Erro: userAgentButton is null
Arquivo-fonte: chrome://useragentswitcher/content/useragentswitcher.js
Linha: 481

Comment 3

[Marcelo]

Tools -> Options -> Security ->
There the mentioned username disapear.
I did a test installing older version (2.0.14) this problem not happen, just in 3.0 version have this bug.
Best regards

Comment 4

[Justin Dolske [:Dolske]]

Looks like you're hitting the issue in bug 435531.