mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 06:35:59 +03:00
[GH-ISSUE #245] Lock Error: Unable to clear lock file, consider deleting Bookmarks.xbel.lock #236
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#236
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 @Tank-Missile on GitHub (Mar 23, 2019).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/245
Software versions
Steps to reproduce
Expected outcome
Bookmarks.xbel generates at the root of all the folders.
Actual outcome
The file fails to generate and I recieve the error in the title. It says to delete Bookmarks.xbel.lock, but it's nowhere to be found in my nextcloud folder or in the web interface.
Debug log
floccus-3.2.10-2019-03-23.log
@marcelklehr commented on GitHub (Mar 23, 2019):
When using the webdav adapter, make sure to provide the URL to the actual webdav share on your server. The options view shows an exemplary URL for nextcloud.
@Tank-Missile commented on GitHub (Mar 23, 2019):
I just made the assumption the base URL was enough. I need to stop configuring things so late at night. It's working now. Sorry for the time waster.
@marcelklehr commented on GitHub (Mar 23, 2019):
No problem :)
@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.