Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

Forced update Firefox ESR 52 broke password manager

  • 4 odpowiedzi
  • 1 osoba ma ten problem
  • 3 wyświetlenia
  • Ostatnia odpowiedź od VGER

more options

When Firefox ESR v52 became available, I did a test install and found that after the upgrade, all my stored passwords were gone. So I rolled back to v45 (?), declined the update to v52 and worked on.

Recently, the update to v52 was forced upon me, without asking, and without my consent. As a result, most of my machines still work, but one doesn't:

- all stored passwords are gone (list is empty) - new passwords are not remembered any more (no popup) - the "reload from keys3.db/signons.sqlite" procedure has no effect (after resetting of the pref signon.importedFromSqlite, it doesn't exist any more on next start. Nothing has been imported into password manager. - I didn't ordinarily use a master password, but now tried to set one. That gave the message "Can't change master password". At least that one I was able to resolve by removing secmod.db from my user profile (shouldn't that be a bug in v53? Why did I have to do that in v52 already?)

Now I even installed the non-ESR v54, and password manager still doesn't work. I've been working on this for days and am getting nowhere. Does anyone have a suggestion that could help me out?

Regards

When Firefox ESR v52 became available, I did a test install and found that after the upgrade, all my stored passwords were gone. So I rolled back to v45 (?), declined the update to v52 and worked on. Recently, the update to v52 was forced upon me, without asking, and without my consent. As a result, most of my machines still work, but one doesn't: - all stored passwords are gone (list is empty) - new passwords are not remembered any more (no popup) - the "reload from keys3.db/signons.sqlite" procedure has no effect (after resetting of the pref signon.importedFromSqlite, it doesn't exist any more on next start. Nothing has been imported into password manager. - I didn't ordinarily use a master password, but now tried to set one. That gave the message "Can't change master password". At least that one I was able to resolve by removing secmod.db from my user profile (shouldn't that be a bug in v53? Why did I have to do that in v52 already?) Now I even installed the non-ESR v54, and password manager still doesn't work. I've been working on this for days and am getting nowhere. Does anyone have a suggestion that could help me out? Regards

Wszystkie odpowiedzi (4)

more options

Did you delete the logins.json file after resetting signon.importedFromSqlite ?

There have been (master password related) issues reported that required to delete secmode.db.


You can rename the logins.json and key3.db (and secmode.db) files to see if that makes the Password Manager work. You need to set a new MP and lose all passwords.

more options

Yes, I also did delete logins.json.

I believe the problem lies elsewhere: Firefox also doesn't save new logins any more. It appears that somehow Firefox can't access its own data storage - even on a completly new install, with newly generated profile.

As described, this is a problem with Firefox v52 and higher. Reinstall the older v45, and all is well again. Only problem is that Firefox will keep forcing the unwanted update, regardless of it breaking things again.

more options

You didn't copy any files to the new profile (especially not logins.json and key3.db)?

You did do a clean install and made sure to delete the Firefox program folder?

more options

Hi,

I did all those things, in all combinations. No success at all.

Regards

cor-el said

You didn't copy any files to the new profile (especially not logins.json and key3.db)? You did do a clean install and made sure to delete the Firefox program folder?

Zmodyfikowany przez VGER w dniu