mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
[GH-ISSUE #1495] No more automatic sync / Scheduled: This profile will be synced soon #984
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#984
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 @misterhsp on GitHub (Dec 23, 2023).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1495
Which version of floccus are you using?
5.0.5
Sync method
Nextcloud Bookmarks
Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.
Firefox
Which version of Nextcloud Bookmarks are you using? (if relevant)
No response
Which version of Nextcloud? (if relevant)
27.1.5
What kind of WebDAV server are you using? (if relevant)
Nextcloud
Describe the Bug
Since the last update of floccus the synchronization does not work automatically after starting the browser. It only works when I click on the small icon at the top right. Before everything was automatic. Has this been changed?
Expected Behavior
'
To Reproduce
Since the last update of floccus the synchronization does not work automatically after starting the browser. It only works when I click on the small icon at the top right. Before everything was automatic. Has this been changed?
Debug log provided
@github-actions[bot] commented on GitHub (Dec 23, 2023):
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 💙
@marcelklehr commented on GitHub (Dec 24, 2023):
Thank your for the feedback!
I can confirm this. The underlying cause is that Manifest v3 background scripts are terminated rather aggressively by the browser which causes the sync process to be interrupted. :/
@misterhsp commented on GitHub (Dec 24, 2023):
Can you change that in floccus or do I have to put up with it?
/hsp
Am 24.12.23 um 15:26 schrieb Marcel Klehr:
@marcelklehr commented on GitHub (Dec 24, 2023):
Oh, yes, I will try to fix this, of course!
@marcelklehr commented on GitHub (Dec 24, 2023):
One idea is to let the sync process run in a visible open tab or window instead, but that's rather ugly :/
@marcelklehr commented on GitHub (Dec 31, 2023):
This should finally be fixed with v5.0.6 released just now -- please report back ❤️
@misterhsp commented on GitHub (Jan 1, 2024):
Danke, funktioniert wieder.
/hsp
Am 31.12.23 um 19:24 schrieb Marcel Klehr:
@misterhsp commented on GitHub (Jan 1, 2024):
upd, sorry ... german
Thanks, it's working again.
/hsp
Am 01.01.24 um 10:34 schrieb Holger Schröder:
@jdelker commented on GitHub (Jan 1, 2024):
Looks good so far.
It may be worth noting, that you need to upgrade all of your clients before this is actually working properly.
Any <5.0.6 client will again create that orphaned lock situation again and block all others.
@truthsword commented on GitHub (Jan 1, 2024):
Uninstalled, reinstalled now on 5.0.6 and this issue remains. Cant force sync up to webdav server. No sync for the past two weeks.
@misterhsp commented on GitHub (Jan 1, 2024):
I can't confirm that. For me the sync with webdav (Nextcloud / xbel
file) works again.
Am 01.01.24 um 19:13 schrieb truthsword:
@marcelklehr commented on GitHub (Jan 1, 2024):
@truthsword Make sure all your firefox instances have v5.0.6, you may have to delete a surplus lock file on your webdav share.
@truthsword commented on GitHub (Jan 1, 2024):
This was it. Had to uninstall the extension from all clients, and delete the lock file.
Would be nice to have notifications when sync fails (mine happened 2 weeks ago). Maybe I've missed that in the settings.
@marcelklehr commented on GitHub (Jan 2, 2024):
Usually you will be notified of failure, this was an extraordinary situation, because I changed the API platform. This is unlikely to happen again soon.
@albirs commented on GitHub (Jan 6, 2024):
where is that lock file located in an nextcloud instance ...?
@marcelklehr commented on GitHub (Jan 6, 2024):
@albirs if you are using Nextcloud Bookmarks, you have no lockfile and will likely only need to make sure all your floccus instances are either v4.x or v5.0.6+. Otherwise when using webdav the lock file is in the same directory as the bookmarks file that is used to sync.
@InfamousUser commented on GitHub (Feb 25, 2024):
Using Floccus v5.0.9, Nextcloud Bookmarks and latest server and experiencing this issue...
@traviss64 commented on GitHub (Feb 26, 2024):
v5.0.9 with Nextcloud and having this issue
@idzyr commented on GitHub (Feb 29, 2024):
v5.0.9 with WebDAV and having this issue
@marcelklehr commented on GitHub (Mar 3, 2024):
Hello everyone, sorry for the delay on this. Please, everyone since this ticket is about v5.0.5 let's all move over to #1548 if you still experience this with v5.0.8 on firefox or v5.0.9 on chrome.
@github-actions[bot] commented on GitHub (Mar 4, 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.