为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

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

详细了解

Lost all address books after upgrade from 68.10 to 78.01

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

more options

Hello to all, I upgraded Thunderbird on my Windows 10 laptop from 68.10 to 78.01 and can't see any address books. Is this upgrade suppose to keep and display your address books? I tried to follow all recommendations that I could find and nothing helped. I even tried to export my address books from my second Windows 10 pc and import to PC 1, and I still couldn't see anything. Finally I had to uninstall (and delete all directories) all versions from laptop 1 and copy everything from laptop 2. Now I'm back on version 68.10 and everything seems to be OK. Is there a bug in conversion to 78.01? Thanks, Yuri

Hello to all, I upgraded Thunderbird on my Windows 10 laptop from 68.10 to 78.01 and can't see any address books. Is this upgrade suppose to keep and display your address books? I tried to follow all recommendations that I could find and nothing helped. I even tried to export my address books from my second Windows 10 pc and import to PC 1, and I still couldn't see anything. Finally I had to uninstall (and delete all directories) all versions from laptop 1 and copy everything from laptop 2. Now I'm back on version 68.10 and everything seems to be OK. Is there a bug in conversion to 78.01? Thanks, Yuri

被采纳的解决方案

Now I understand why address book was not migrated. Unfortunately ti should have been made clear when automatic migration happened. Now I'll wait until this "bug" will be fixed.

定位到答案原位置 👍 0

所有回复 (6)

more options
more options

Also, Version 78.1.0 is available - Help > About

more options

Was this issue fixed in 78.1.0? Was it even recognized as an issue?

more options
more options

选择的解决方案

Now I understand why address book was not migrated. Unfortunately ti should have been made clear when automatic migration happened. Now I'll wait until this "bug" will be fixed.

more options

I believe the bug has been fixed in 78.1.0, which is why I posted the link to the release notes so that you could read for yourself the fixes that were done in this release.