mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #530] Error: Invalid bookmark #373
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#373
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @eleksis on GitHub (May 13, 2020).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/530
Describe the bug
floccus gets stuck in syncing state. I checked 'Trigger sync from scratch' and ran manually. Got this error: Error: Invalid bookmark: {"title":"","type":1,"url":"data:","parentGuid":"9ubIr19mqUSH"}
To Reproduce
Don't know how it came to this broken state.
Expected behavior
Sync sucessfully.
Desktop (please complete the following information):
Debug log
Additional context
I am using Firefox sync, but only for open tabs (not bookmarks).
Second machine is also Linux+Firefox
@marcelklehr commented on GitHub (May 19, 2020):
That's a separator line messing up your bookmarks. :(
Floccus doesn't deal with separator lines properly, yet, because their not really supported in Chrome and I haven't had the chance to make up my mind on how to proceed. Removing the separator and the
data:links from your XBEL should fix this after a sync from scratch.@eleksis commented on GitHub (Jun 3, 2020):
Thanks, that helped.
@github-actions[bot] commented on GitHub (Mar 21, 2023):
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.