搜索 | 用户支持

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

Learn More

top sites not shown in new tab page after updating to 61.0

  • 2 个回答
  • 1 人有此问题
  • 13 次查看
  • 最后回复者为 nibikibaba

more options

The new tab page now shows only a grey firefox icon at the top left corner. Clicking on that would show the "Let Get Started" box with some 'tours' about the new features.

Here are some of the about:config settings related to browser.newtabpage:

browser.newtabpage.enabled: true (default). ....activity-stream.migrationExpired: true ....activity-stream.prerender: false ....activity-stream.topStiesRows: 2 ....blocked: {"....":1,"...."...} ....enhanced: true ....introShown: true ....pinned:[{"url":"....".... ....storageVersion: 1 FYI I didn't change any of them.

The new tab page now shows only a grey firefox icon at the top left corner. Clicking on that would show the "Let Get Started" box with some 'tours' about the new features. Here are some of the about:config settings related to browser.newtabpage: browser.newtabpage.enabled: true (default). ....activity-stream.migrationExpired: true ....activity-stream.prerender: false ....activity-stream.topStiesRows: 2 ....blocked: {"....":1,"...."...} ....enhanced: true ....introShown: true ....pinned:[{"url":"....".... ....storageVersion: 1 FYI I didn't change any of them.

被采纳的解决方案

  1. open about:support & go to your profile folder
  2. close all running instances of firefox
  3. in your profile rename the "storage" folder to "storage.bak"
  4. then try starting up firefox again

Is it working now?

定位到答案原位置 👍 0

所有回复 (2)

more options

选择的解决方案

  1. open about:support & go to your profile folder
  2. close all running instances of firefox
  3. in your profile rename the "storage" folder to "storage.bak"
  4. then try starting up firefox again

Is it working now?

more options

Thanks for the reply. Yes it is working now.

I solved this myself when I was looking into another problem with Tab Session Manager triggered by the FF61.0 update. The Tab Session Manager help suggested the same solution: removing the 'storage' folder, which basically resets the IndexedDB storage which had somehow been corrupted during the update to 61.0.