mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
[GH-ISSUE #1548] Bookmarks can't be synchronized and show "Scheduled" #1020
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#1020
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 @Ganya-A on GitHub (Feb 21, 2024).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1548
Which version of floccus are you using?
5.0.8 5.0.9
Sync method
WebDAV
Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.
Edge
Which version of Nextcloud Bookmarks are you using? (if relevant)
No response
Which version of Nextcloud? (if relevant)
No response
What kind of WebDAV server are you using? (if relevant)
jianguoyun
Describe the Bug
I can't get both of my computers to sync.
Scheduled：This profile will be synced soon. We're either waiting for other devices of yours, or other profiles on this device, to finish syncing.
Expected Behavior
To Reproduce
Debug log provided
@github-actions[bot] commented on GitHub (Feb 21, 2024):
Hello 👋
Thank you for taking the time to open this issue with floccus. I know it's frustrating when software
causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at
and if possible solved.
I'm Marcel and I created floccus and have been maintaining it ever since.
I currently work for Nextcloud which leaves me with less time for side projects like this one
than I used to have.
I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it.
Until then, please be patient.
Note also that GitHub is a place where people meet to make software better together. Nobody here is under any obligation
to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can
collaborate to make this software better. For everyone.
Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge
and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and
try to fix the odd bug yourself. Everyone will be thankful for extra helping hands!
One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the forum,
to twitter or somewhere else. But this is a technical issue tracker, so please make sure to
focus on the tech and keep your opinions to yourself.
I look forward to working with you on this issue
Cheers 💙
@Syzygy33 commented on GitHub (Feb 28, 2024):
try to delete the .lock file
@Ganya-A commented on GitHub (Feb 29, 2024):
After deleting the. lock file, it will appear soon.
@Syzygy33 commented on GitHub (Mar 1, 2024):
or use Google drive？
---- Replied Message ----
| From | @.> |
| Date | 03/01/2024 07:31 |
| To | floccusaddon/floccus @.> |
| Cc | Syzygy33 @.>,
Comment @.> |
| Subject | Re: [floccusaddon/floccus] Bookmarks can't be synchronized and show“Scheduled” (Issue #1548) |
Which version of floccus are you using?
5.0.8 5.0.9
Sync method
WebDAV
Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.
Edge
Which version of Nextcloud Bookmarks are you using? (if relevant)
No response
Which version of Nextcloud? (if relevant)
No response
What kind of WebDAV server are you using? (if relevant)
jianguoyun
Describe the Bug
I can't get both of my computers to sync. Scheduled：This profile will be synced soon. We're either waiting for other devices of yours, or other profiles on this device, to finish syncing.
Expected Behavior
To Reproduce
Debug log provided
I have provided a debug log file
try to delete the .lock file
After deleting the. lock file, it will appear soon.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>
@marcelklehr commented on GitHub (Mar 3, 2024):
Please make sure
Judging from the chrome webstore statistics there are still around 800 Chrome instances on v5.0.6, which has this bug.
@Ganya-A commented on GitHub (Mar 8, 2024):
I've updated all device versions to 5.0.9, two EDGE, and one mobile browser, and I'm still having this problem.
@marcelklehr commented on GitHub (Mar 8, 2024):
So, this should only really be a problem when syncing via WebDAV like @Ganya-A and @idzyr and @beyercj
@InfamousUser is syncing via Nextcloud Bookmarks, which should automatically timeout its lock. Is this still happening for you?
@traviss64 are you syncing via Nextcloud Bookmarks or via Nextcloud files (ie. webdav)?
@idzyr commented on GitHub (Mar 9, 2024):
@marcelklehr
I have the same issue as the original post, but I'm using a PC with Chrome(v122.0.6261.112). I tried deleting the lock file, but after a while, it stops working again.
@marcelklehr commented on GitHub (Mar 9, 2024):
This should be resolved with v5.0.10, please let me know if it works :)
@InfamousUser commented on GitHub (Mar 9, 2024):
Updated to v5.0.10 on Chrome, no change.
@beyercj commented on GitHub (Mar 11, 2024):
Updated to v5.0.10 on Firefox 115.8.0esr for Linux and to v5.0.11 on Android 11 on Samsung Galaxy A12, no change either on webdav.smartdrive.web.de (webspace almost full). However, synchronisation worked fine on webdav.vodafonemail.de (webspace almost empty), so might not have anything to do with floccus.
@marcelklehr commented on GitHub (Mar 12, 2024):
So, this issue usually stems from a leftover lock file that prevents all clients from syncing. v5.0.10 should mitigate that by forcing floccus to sync anyway, if it has waited long enough. If this does not fix this for you all, then we might have a more serious issue of an interrupted sync process. This would be the case if for example if floccus does sometimes start to sync but then stops, likely after about 5mins, only to then show the "scheduled Sync" message one minute later, which again stems from the leftover lock file. On firefox I think you can also verify if this is the problem by opening the browser debug log. The browser will then no longer interrupt the sync process and thus floccus should sync correctly after some time waiting for the lock to expire and go back to an "All good" green status, while the debug window is open.
Here's how to open the debug window:
Firefox
about:debuggingThis firefoxdebugbutton next to floccus entry to open the consoleNot sure, if this will work in chrome, but you may try:
Chrome
chrome://extensionsDeveloper modedist/html/background.htmlbutton in floccus' entry next to "Inspect views: " to open the console@InfamousUser commented on GitHub (Mar 12, 2024):
I am receiving "QUEUING POST", "FETCHING POST", "Receiving response for POST" and then "Resource is locked, trying again soon" in the Floccus logs. I should note that it did sync the folders to the server, but none of the actual bookmarks are populated.
@marcelklehr commented on GitHub (Mar 17, 2024):
@InfamousUser You will need to wait until the lock is cleared for the above thing with the debug window to work. Only unpopulated folders is a bad sign, though...
@InfamousUser commented on GitHub (Mar 17, 2024):
How long do I need to wait? Sever has been off for the past few days, I just turned it on and still the same problem. Is there a way to force this or what am I supposed to do?
@marcelklehr commented on GitHub (Mar 17, 2024):
Doesn't matter anymore, I've been able to reproduce this now and can debug from there. It looks like Chrome blatantly shuts down extension service workers after running some amount of minutes. There's not gonna be an easy fix for this, I think. Should still be doable though
@smth commented on GitHub (Mar 29, 2024):
I also have this problem. Two Firefox browsers using v5.0.10 (though one was recently on 5.0.5). My server does have a lock file on it.
@cng10001 commented on GitHub (Apr 3, 2024):
Add a new account and use other ways of sync for now.Hope the author solve the problem soon.
@truthsword commented on GitHub (Apr 3, 2024):
Updated Firefox from 5.0.8 to 5.0.10 and within a short time the lock file imposed itself. Is rollback possible? I deleted the lock file, but can't do that regularly. I'm using WebDAV.
@cng10001 commented on GitHub (Apr 3, 2024):
I delete the lock file ,then remove my account and re-add it. You can try this too, no loss anyway
@truthsword commented on GitHub (Apr 3, 2024):
No need to remove account. Disable all Floccus extensions. Delete lock file. Enable all Floccus extensions. Not something one wants to do multiple times a day.
@marcelklehr commented on GitHub (Apr 5, 2024):
I'm working on the fix for this. It's quite involved, but I should be able to provide a beta soon, for you to test 🚀
@InfamousUser commented on GitHub (Apr 5, 2024):
Great to hear it is getting fixed! Thanks for the update!
@marcelklehr commented on GitHub (Apr 6, 2024):
Hello everyone, there's now a beta release available which should fix this issue: https://github.com/floccusaddon/floccus/releases/tag/v5.0.12-beta.1
Firefox
On firefox you should be able to install this by
about:debugging-> "This Firefox" -> Load temporary extension -> and selecting the unzipped folderChrome
On chrome you should be able to install this by
chrome://extensionsAndroid
On android you should be able to install this by
Important
Let me know how it goes ✌️
@cng10001 commented on GitHub (Apr 8, 2024):
It seems the problem still exits
@marcelklehr commented on GitHub (Apr 8, 2024):
@cng10001 You will still need to wait or remove the lock manually, initially, as described above. Afterwards it shouldn't get stuck like this anymore.
@marcelklehr commented on GitHub (Apr 14, 2024):
Any other testers? Would be great if a few of you could test this, otherwise I have to release it untested :S
@InfamousUser commented on GitHub (Apr 14, 2024):
Well, unlike the previous version, this one did manage to sync something. It synced around 150 bookmarks before going to the "Scheduled" stage and stopping there. Errors in the log are identical to the post https://github.com/floccusaddon/floccus/issues/1548#issuecomment-1992606654 or being E017 network error which changes to the "This profile will be synced soon..." one upon depressing the sync now button.
It is periodically switching between syncing and scheduled with syncing only for a few seconds but no additional bookmarks being synced.
@marcelklehr commented on GitHub (Apr 14, 2024):
@InfamousUser Thank you for taking it for a spin! Are there any other floccus instances running that haven't been updated to the beta version, yet?
@InfamousUser commented on GitHub (Apr 14, 2024):
There is the original Floccus, the beta doesnt update it but make an additional extension unfortunately. It had its autosync disabled though and hasn't synced as far as I'm aware and the last error in its log is 17.03.2024. I can delete it if you think it's interfering in some way?
@marcelklehr commented on GitHub (Apr 14, 2024):
Mh, probably best to disable the original extension instance, yeah
@InfamousUser commented on GitHub (Apr 14, 2024):
I disabled the real extension in settings. It seems to be randomly syncing more bookmarks but this is not what I would call a working fix. It has synced another 100 or so bookmarks. When you press the sync it latches but then it keeps switching between syncing and scheduled. Bu then after a while it "finishes" and you have to trigger it again because it has not synced the bookmarks.
@cng10001 commented on GitHub (Apr 17, 2024):
Maybe my problem is I was still using a lower version of chrome,
I updated the browser and I'll watch it for more days
@marcelklehr commented on GitHub (Apr 21, 2024):
@InfamousUser Can you confirm whether it syncs for roughly 5 minutes, at least, before it switches back to "scheduled"?
@marcelklehr commented on GitHub (Apr 21, 2024):
Chrome version may be interesting as well, indeed. Chrome v110+ may be necessary for some of this to work properly
@InfamousUser commented on GitHub (Apr 24, 2024):
I do not and cannot have Chrome v110+ due to Google blocking updates on older Windows so count me out for testing that...
@marcelklehr commented on GitHub (Apr 24, 2024):
Oh Wow! So you do have pre v110 Chrome, so the fix I built may work after all. Sorry about the Chrome updates!
@InfamousUser commented on GitHub (Apr 24, 2024):
Geez, never thought that'd be the issue! I can try it on a different PC, with newer browser, but I have a feeling that will work since it doesn't really help! Will get back to you with the results!
@marcelklehr commented on GitHub (Apr 25, 2024):
It's not the root cause, but part of my fix only works post v110
@marcelklehr commented on GitHub (Apr 26, 2024):
Alright, since it works for me I'll roll this out stage-wise in production now to get people to test it.
@marcelklehr commented on GitHub (May 3, 2024):
Staged roll-out failed for some reason, so now this is on prod 100% 🙈
Anyway. @Ganya-A and @idzyr and @beyercj Are you on v5.0.12 already? Does it work now after removing the lock file manually once?
@InfamousUser commented on GitHub (Jul 21, 2024):
Just to confirm the fix works for me, but everyone already knows I guess.
@marcelklehr commented on GitHub (Jul 21, 2024):
Thank you @InfamousUser always good to get confirmation :)
@ivanjx commented on GitHub (Sep 17, 2024):
where is the .lock file on nextcloud?
@marcelklehr commented on GitHub (Sep 17, 2024):
@ivanjx please open a new discussion or a new issue
@joshqou commented on GitHub (Nov 18, 2024):
This can still happen on version
5.2.7if you start and immediately cancel a sync. i.e: accidentially double-click the sync now button. There should really be a button to manually remove the lock file so users don't have to open devtools just to get their bookmarks syncing again@marcelklehr commented on GitHub (Nov 18, 2024):
@joshqou Good idea! Can you open a feature request for this?
@joshqou commented on GitHub (Nov 18, 2024):
@marcelklehr Created at #1769
@github-actions[bot] commented on GitHub (Nov 19, 2025):
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.