mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 14:45:59 +03:00
[GH-ISSUE #411] E023: sync does not succeed because of lock file, even though no lock file exists #320
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#320
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 @aktentasche on GitHub (Nov 26, 2019).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/411
Describe the bug
On my linux machine I am syncing my bookmarks to a self hosted nextcloud. Now I wanted to have the same bookmarks on my windows machine. However, a fresh sync fails, even though the mentioned lock file does not exist.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The initial sync succeeds
Desktop (please complete the following information):
Server (please complete the following information):
Debug log
@aktentasche commented on GitHub (Nov 26, 2019):
See also See also: https://github.com/marcelklehr/floccus/issues/347#issuecomment-523906322
ping @bhlevca
I have a hunch that it might be the outdated chromium version on Windows. Will check tomorrow.
@aktentasche commented on GitHub (Nov 26, 2019):
relevant folder
@marcelklehr commented on GitHub (Nov 27, 2019):
The error message is somewhat misleading. The problem is that the webdav URL is wrong. Try using the URL in the bottom left of your screenshot.
@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.