搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Firefox upgrade loses website logins

  • 2 个回答
  • 3 人有此问题
  • 12 次查看
  • 最后回复者为 Davik03

more options

Fore years, I saved many website logins (user ID, password) in Firefox. Since upgrading to v 67.0.x in the middle of June 2019, FF lost all the stored data and I've been unable to login to website accounts using stored FF logins: had to use either manual logins or create a new account. Looking at the tools/options/security page and the stored login data, I've had to re-create any login for a site I use since 14 June. I'm at 67.0.4 now and getting really pissed off at this. What happened? What's been done to stop it happening again?

Fore years, I saved many website logins (user ID, password) in Firefox. Since upgrading to v 67.0.x in the middle of June 2019, FF lost all the stored data and I've been unable to login to website accounts using stored FF logins: had to use either manual logins or create a new account. Looking at the tools/options/security page and the stored login data, I've had to re-create any login for a site I use since 14 June. I'm at 67.0.4 now and getting really pissed off at this. What happened? What's been done to stop it happening again?

所有回复 (2)

more options

We have recently seen cases reported about AVG software (AVG Password Protection) that prevents Firefox from accessing logins.json with the result that Firefox renames the file and add .corrupt (logins.json.corrupt) and starts with a new file.

See:

Mozilla has created an extension to recover logins.json from a possibly numbered logins.json.corrupt file.

more options

cor-el said

We have recently seen cases reported about AVG software (AVG Password Protection) that prevents Firefox from accessing logins.json with the result that Firefox renames the file and add .corrupt (logins.json.corrupt) and starts with a new file. See: Mozilla has created an extension to recover logins.json from a possibly numbered logins.json.corrupt file.

useful - Yes and No At least, I know what's caused it. But the fix per mozilla is basically a start again exercise. Up until today, I'd re-input 4 login identities: and at this stage, that's all there were. I ran the latest mozilla plug-in, chose the recommended corrupt json (there were 2, the recommended one was the oldest), the screen blanked and then browser UI re-appeared. To test, I chose to login to one of the bookmarked sites, failed: a fresh login panel presented. I know this was a correct saved version since I used it this morning. But now - trashed. Only one of the 4 new ID's survived this change. Start again with the others. Moszilla should test this more extensively.