mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 06:35:59 +03:00
[GH-ISSUE #1550] Unexpected Synchronization Error in Waterfox #1022
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#1022
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 @balthanon on GitHub (Feb 26, 2024).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1550
Which version of floccus are you using?
5.0.8; tried updating to 5.0.9 as well
Sync method
Google Drive
Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.
Waterfox G6.0.9
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)
No response
Describe the Bug
Floccus is failing to sync bookmarks from Waterfox; possibly a result of the computer freezing upon resuming from sleep and needing a hard shutdown, though Chrome was also open at that time and isn't displaying the same issues. It's possible that floccus was syncing at the time that was happening if it started immediately (the freeze happened within seconds of startup though). I've tried restarting the browser, computer, updating the extension, forcing a sync, pulling bookmarks, and clearing the cache in the extension. I haven't uninstalled and reinstalled the extension yet, deleted and recreated the profile, or pushed the profile.
The debug logs aren't particularly helpful from what I can see:
2024-02-26T00:19:42.174Z Starting sync process for account Google Drive: bookmark-menu.xbel
2024-02-26T00:19:42.319Z onSyncStart: begin
2024-02-26T00:19:44.607Z onSyncStart: completed
2024-02-26T00:19:44.611Z Syncing failed with An unexpected error occurred
2024-02-26T00:19:44.613Z onSyncFail
At least 4 or 5 other browsers are having no issues accessing the same file. Additionally, two other smaller profiles are syncing fine, though I did notice that the bookmark menu had an extra folder that matched one of the other profiles (the bookmark toolbar).
Expected Behavior
Waterfox syncing the bookmarks menu normally.
To Reproduce
Honestly not sure how to reproduce the error other than possibly deliberately forcing a crash. Debug logs are provided above since they don't contain any private data.
Debug log provided
@github-actions[bot] commented on GitHub (Feb 26, 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 💙
@balthanon commented on GitHub (Feb 29, 2024):
I was holding off on doing this in case there was troubleshooting/analysis that might require delving into the issue while it was active, but removing the profile and then adding it back in seems to have resolved the issue. Assuming you don't have enough data based off of what I've provided, this issue can probably be closed. (Or if it is left open and happens again, I'll try to identify commonalities and post.)
@marcelklehr commented on GitHub (Mar 2, 2024):
Mmh, it might be that waterfox is missing some extensions functionality that floccus v5 now relies on. Generally, I try to support mainline browsers only, while supporting forks on a best effort basis. Can you find out what the equivalent Firefox version would be to Waterfox G6.0.9? (I assume it's based on some Firefox version)
@balthanon commented on GitHub (Mar 3, 2024):
Looks like security fixes are through Firefox ESR 115.8 at least-- I'll see if I can track down a better answer on feature parity. I think it is based on the latest ESR release at any given time though (which should be 115.8, so that tracks). Not putting too much effort into the forks makes sense.
@marcelklehr commented on GitHub (May 15, 2024):
Since you solved it by reinstalling, I'll close this for now.
@github-actions[bot] commented on GitHub (May 16, 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.