mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #710] Sync stuck in chrome floccus v4.3.0 after syncing bookmarks on firefox v.4.4.2 #454
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#454
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 @adrianharabula on GitHub (Oct 28, 2020).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/710
Describe the bug
On chrome latest available version as of today is 4.3.0, while in firefox it is v4.4.2.
Xbel sync works fine from firefox floccus v4.4.2, but the sync process gets stuck in chrome when using floccus v4.3.0.
No strange lines in logs found.
@marcelklehr commented on GitHub (Oct 28, 2020):
This might be due to an uncleared lock file. v4.4.x will soon be published for chrome as well, though.
@adrianharabula commented on GitHub (Oct 28, 2020):
Here is a list of steps I've tried:
Many thanks for the answer!
@marcelklehr commented on GitHub (Oct 29, 2020):
You can try checking the browser logs as follows to see what is going wrong:
@ixmu commented on GitHub (Jan 4, 2021):
Hope to update the plugin version in the chrome store.
@marcelklehr commented on GitHub (Jan 21, 2021):
Update is rolled out for Chrome and Edge. I'm closing this for now, feel free to shout if this is still an issue with the newest version.
@adrianharabula commented on GitHub (Jan 21, 2021):
Many thanks!
@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.