搜索 | 用户支持

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

详细了解

после того как Ваш браузер запросил синхронизацию пропали все пароли!!!

  • 23 个回答
  • 2 人有此问题
  • 2 次查看
  • 最后回复者为 Tonnes

more options

Добрый день.... ваш браузер попросил повторить синхронизацию.... после чего пропали все пароли к сайтам.....!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Добрый день.... ваш браузер попросил повторить синхронизацию.... после чего пропали все пароли к сайтам.....!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

被采纳的解决方案

SOLVED setup FF 56 on another PC... it synch good.. then copy files key3 and logins.json.. to my pc... all good... but stil cant understand wil my PC did not synch automaticaly!!??

定位到答案原位置 👍 0

所有回复 (3)

more options

sorry for my bad russian )) will try to explain... PC FF logins are empty... file logins.json.corrupt after renaming to logins.json and turning on FF again renamed in .corrupt... and one more thing... logins.json.corrupt is binary file not text... i cant understand how to restore my logins stored in androin in to desctop version!!

and i`m affraid that synch of android.. no can delete logins on them

由s212于修改

more options

选择的解决方案

SOLVED setup FF 56 on another PC... it synch good.. then copy files key3 and logins.json.. to my pc... all good... but stil cant understand wil my PC did not synch automaticaly!!??

more options

Well done.

I cannot fully explain why this happened. It’s not described in the release notes for your version (of which we’re not sure whether this is 55.0, 55.0.1, 55.0.2 or 55.0.3 - you should of course use the latest - and you didn’t name the Android version either although I assume that’s trivial), but there have been reports of profile corruption with that version. Looking at this and this bug (and perhaps this and this bug) however tells us other versions may be affected too.

If you really want to find out what happened, reproduce the issue and look at the Browser Console or use about:sync-log to see if any logs match with what’s posted there. These logs may actually still exist, so you don’t even need to reproduce. One of these bugs mentions A/V software to be a possible cause too.

  1. 1
  2. 2