[GH-ISSUE #411] E023: sync does not succeed because of lock file, even though no lock file exists #320

Closed
opened 2026-02-25 22:36:48 +03:00 by kerem · 4 comments
Owner

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:

  1. Sync bookmarks to nextcloud from Linux machine
  2. Fresh install of ungoogled-chromium on Windows
  3. Install floccus via chrome web store
  4. Start sync from scratch via xbel stored on nextcloud

Expected behavior
The initial sync succeeds

Desktop (please complete the following information):

  • OS: Win 10 / Arch Linux
  • Browser: ungoogled chromium
  • Browser Version: 67.0.3396.87 (Win) / 78.0.3904.108-1 (Linux)
  • Floccus version: 3.5.1
  • Floccus sync method: webdav/xbel

Server (please complete the following information):

  • OS: Debian 10
  • Nextcloud version: 16.0.5
  • Bookmarks app version: n/a

Debug log

2019-11-26T22:47:13.167Z Starting sync process for account foo@bar.com
2019-11-26T22:47:13.172Z onSyncStart: begin
2019-11-26T22:47:13.172Z https://bar.com/nextcloud/Lesezeichen/privat.xbel.lock
2019-11-26T22:47:21.567Z https://bar.com/nextcloud/Lesezeichen/privat.xbel.lock
2019-11-26T22:47:30.086Z https://bar.com/nextcloud/Lesezeichen/privat.xbel.lock
2019-11-26T22:47:37.642Z https://bar.com/nextcloud/Lesezeichen/privat.xbel.lock
2019-11-26T22:47:45.704Z https://bar.com/nextcloud/Lesezeichen/privat.xbel.lock
2019-11-26T22:47:53.376Z https://bar.com/nextcloud/Lesezeichen/privat.xbel.lock
2019-11-26T22:48:01.429Z Syncing failed with E023: Freigabe der Lock-Datei war nicht erfolgreich. Erwägen Sie Lesezeichen/privat.xbel.lock von Hand zu löschen.
2019-11-26T22:48:01.431Z onSyncFail
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: 1. Sync bookmarks to nextcloud from Linux machine 2. Fresh install of ungoogled-chromium on Windows 3. Install floccus via chrome web store 4. Start sync from scratch via xbel stored on nextcloud **Expected behavior** The initial sync succeeds **Desktop (please complete the following information):** - OS: Win 10 / Arch Linux - Browser: ungoogled chromium - Browser Version: 67.0.3396.87 (Win) / 78.0.3904.108-1 (Linux) - Floccus version: 3.5.1 - Floccus sync method: webdav/xbel **Server (please complete the following information):** - OS: Debian 10 - Nextcloud version: 16.0.5 - Bookmarks app version: n/a **Debug log** ``` 2019-11-26T22:47:13.167Z Starting sync process for account foo@bar.com 2019-11-26T22:47:13.172Z onSyncStart: begin 2019-11-26T22:47:13.172Z https://bar.com/nextcloud/Lesezeichen/privat.xbel.lock 2019-11-26T22:47:21.567Z https://bar.com/nextcloud/Lesezeichen/privat.xbel.lock 2019-11-26T22:47:30.086Z https://bar.com/nextcloud/Lesezeichen/privat.xbel.lock 2019-11-26T22:47:37.642Z https://bar.com/nextcloud/Lesezeichen/privat.xbel.lock 2019-11-26T22:47:45.704Z https://bar.com/nextcloud/Lesezeichen/privat.xbel.lock 2019-11-26T22:47:53.376Z https://bar.com/nextcloud/Lesezeichen/privat.xbel.lock 2019-11-26T22:48:01.429Z Syncing failed with E023: Freigabe der Lock-Datei war nicht erfolgreich. Erwägen Sie Lesezeichen/privat.xbel.lock von Hand zu löschen. 2019-11-26T22:48:01.431Z onSyncFail ```
kerem 2026-02-25 22:36:48 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@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.

<!-- gh-comment-id:558854894 --> @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.
Author
Owner

@aktentasche commented on GitHub (Nov 26, 2019):

grafik

relevant folder

<!-- gh-comment-id:558855251 --> @aktentasche commented on GitHub (Nov 26, 2019): ![grafik](https://user-images.githubusercontent.com/17249161/69679887-95628280-10a9-11ea-81e8-b88aa3be1a9c.png) relevant folder
Author
Owner

@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.

<!-- gh-comment-id:559286337 --> @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.
Author
Owner

@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.

<!-- gh-comment-id:1477332017 --> @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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/floccus#320
No description provided.