搜索 | 用户支持

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

详细了解

Places.sqlite file is corrupted when I log out of linux

  • 3 个回答
  • 1 人有此问题
  • 1 次查看
  • 最后回复者为 cor-el

more options

I'm running Fedora 13 and have just installed Firefox 23, leaving the RPM-supplied version in place (as I plan on upgrading Fedora sooner or later anyway). I created a second profile for the new installation, and imported bookmarks and other configuration. When I close Firefox and re-start, no problems; when I log out of Linux, though, and log on again, I find a places.sqlite.corrupt file in my profile directory (containing my real bookmarks) and a tiny places.sqlite containing default bookmarks. Obviously renaming the "corrupt" file to the right name gets my bookmarks back.

I'm running Fedora 13 and have just installed Firefox 23, leaving the RPM-supplied version in place (as I plan on upgrading Fedora sooner or later anyway). I created a second profile for the new installation, and imported bookmarks and other configuration. When I close Firefox and re-start, no problems; when I log out of Linux, though, and log on again, I find a places.sqlite.corrupt file in my profile directory (containing my real bookmarks) and a tiny places.sqlite containing default bookmarks. Obviously renaming the "corrupt" file to the right name gets my bookmarks back.

被采纳的解决方案

Did you try to make Firefox generate a new places.sqlite file by removing all places files?

That should make Firefox use a JSON backup in the bookmarkbackups folder to create a new places.sqlite database file.

定位到答案原位置 👍 1

所有回复 (3)

more options

选择的解决方案

Did you try to make Firefox generate a new places.sqlite file by removing all places files?

That should make Firefox use a JSON backup in the bookmarkbackups folder to create a new places.sqlite database file.

more options

Aha! Yes, that worked. (My formhistory.sqlite was also getting corrupted, as I discovered shortly after posting this, and the same trick worked for it too.) Thank you!

more options

It is possible that the current Firefox version uses a more recent SQLite version then was used in older SQLite database files and then things can go wrong (there is usually migration code when updating).