Avatar for Username

Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Learn More

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

Firefox 60.3.0esr (64-bit) on Linux does not read logins.json after latest update

  • 1 risposta
  • 1 ha questo problema
  • 16 visualizzazioni
  • Ultima risposta di cor-el

joe20
joe20
more options

I updated Firefox to version 60.3.0esr (64-bit) and all my saved logins disappeared. My profile folder is correct, it remembers my other settings. Also logins.json and key3.db and key4.db are in that folder, and logins.json contains all my saved logins. But I can see only one saved login in Firefox Saved Logins list, the last one created. I read about Firefox switching from key3.db to key4.db, I'm not sure if this is related. Also it looks like Firefox update messed up my settings somehow because "use master password" is not set anymore. Either way I'd like to get all my logins back, how can I do that? Thanks,

Joe

I updated Firefox to version 60.3.0esr (64-bit) and all my saved logins disappeared. My profile folder is correct, it remembers my other settings. Also logins.json and key3.db and key4.db are in that folder, and logins.json contains all my saved logins. But I can see only one saved login in Firefox Saved Logins list, the last one created. I read about Firefox switching from key3.db to key4.db, I'm not sure if this is related. Also it looks like Firefox update messed up my settings somehow because "use master password" is not set anymore. Either way I'd like to get all my logins back, how can I do that? Thanks, Joe

Modificato da joe20 il

Tutte le risposte (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

From what Firefox version did you update?

Firefox versions prior to Firefox 58 used the key3.db key file. If you have used a Firefox version before that used key4.db and not key3.db then you might have already had a key4.db file that isn't compatible. You can backup the current logins.json and key4.db and key3.db files to another location and try to remove the key3.db file to see if that makes the logins.json file work. You may have to remove pkcs11.txt and secmode.db as well.