Die Funktionalität dieser Website ist durch Wartungsarbeiten eingeschränkt, die Ihr Erlebnis verbessern sollen. Wenn ein Artikel Ihr Problem nicht löst und Sie eine Frage stellen möchten, können Sie unsere Gemeinschaft über @FirefoxSupport auf Twitter, /r/firefox oder Reddit fragen.

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Updated bookmark name not showing in 'Show all bookmarks'

  • 2 Antworten
  • 1 hat dieses Problem
  • 8 Aufrufe
  • Letzte Antwort von richardgb

more options

After editing some bookmarks I went to 'Show all bookmarks' to check their displayed order. However, both the edited and unedited versions of the bookmark name were showing, which is confusing - there appears to be twice the number of bookmarks! The same duplication appears when I look at the drop-down list of bookmarks under the Bookmark tab. When I open one of the incorrectly-displayed bookmarks and go to 'Edit this bookmark' the edited name is correctly display. Isn't an edited bookmark supposed to replace the unedited version?

After editing some bookmarks I went to 'Show all bookmarks' to check their displayed order. However, both the edited and unedited versions of the bookmark name were showing, which is confusing - there appears to be twice the number of bookmarks! The same duplication appears when I look at the drop-down list of bookmarks under the Bookmark tab. When I open one of the incorrectly-displayed bookmarks and go to 'Edit this bookmark' the edited name is correctly display. Isn't an edited bookmark supposed to replace the unedited version?

Ausgewählte Lösung

Thanks Cor-el.

Re sync used for bookmarks? Yes. Your support pages asked to check whether the Properties of the places.sqlite file showed 'Read only' under 'Attributes' as 'Read only' may cause sync problems. However, the box was unchecked.

Re 'Verify integrity', the results are: + The places.sqlite database is sane + The favicons.sqlite database is sane

This would indicate all is in order and, indeed, only the edited bookmarks are now visible. Whether this self-correction was due to Firefox syncing while not in use, I cannot say. For the moment, though, all seems well.

Diese Antwort im Kontext lesen 👍 0

Alle Antworten (2)

more options

Are you possibly using Sync to sync the bookmarks as that can be a possible cause for this corruption ?


If you use Sync then best is to disconnect Sync temporarily during troubleshooting.

This can be caused by a problem with the places.sqlite and favicons.sqlite databases in the Firefox profile folder.

  • use "Verify Integrity" button on the "Help -> More Troubleshooting Information" (about:support) page

If errors are reported with "Verify Integrity", close and restart Firefox or reboot and retry.

If "Verify Integrity" cannot repair places.sqlite, rename/remove all places.sqlite and favicons.sqlite files in the Firefox profile folder with Firefox closed. Firefox will rebuild places.sqlite and restore the bookmarks from a recent JSON backup in the bookmarkbackups folder.

  • keep a backup copy of places.sqlite in case a new places.sqlite database has to be created

You lose the history when a new places.sqlite is created.

See also:

You can use the button on the "Help -> More Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:profiles page.

more options

Ausgewählte Lösung

Thanks Cor-el.

Re sync used for bookmarks? Yes. Your support pages asked to check whether the Properties of the places.sqlite file showed 'Read only' under 'Attributes' as 'Read only' may cause sync problems. However, the box was unchecked.

Re 'Verify integrity', the results are: + The places.sqlite database is sane + The favicons.sqlite database is sane

This would indicate all is in order and, indeed, only the edited bookmarks are now visible. Whether this self-correction was due to Firefox syncing while not in use, I cannot say. For the moment, though, all seems well.