搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

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

  • 3 回覆
  • 1 有這個問題
  • 8 次檢視
  • 最近回覆由 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).