mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
[GH-ISSUE #1825] If you have a local file open in Chrome during Tabs sync then the other instance of Chrome goes haywire, opened the same tab 40 times. #1227
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#1227
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 @Presareo on GitHub (Jan 13, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1825
Which version of floccus are you using?
5.4.2.1
How many bookmarks do you have, roughly?
This is for the sync feature, was about 6 to 8 tabs.
Are you using other means to sync bookmarks in parallel to floccus?
I am logged into chrome with bookmark syncing. No tab syncing, but there is tab group syncing (which is more like temporary bookmark containers).
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.
Chrome Version 131.0.6778.265
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
If a local file Tab is part of the sync it shows an error state when syncing tabs to another machine that does not have that file, once in error state it keeps opening endless copies of a single tab that was part of the sync. The issue is 2 parts:
Error handling should stop the sync, notify the user, and point to logs, it should not continue at all in my opinion but even if it does continue syncing the data it should never execute actions on the PC while in an error state.
Expected Behavior
My tabs to be synced.
To Reproduce
Install extension on 2 PCs and set up tab syncing. One tab should be pointed to a file:/// protocol. Can also do it on one PC with 2 profiles by moving / deleting the file after its been synced up but before the 2nd profile is loaded to sync down the tabs.
floccus-5.4.2-2025-01-13-redacted.log
Debug log provided
@github-actions[bot] commented on GitHub (Jan 13, 2025):
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 a few years ago, 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!
To continue the development and maintenance of this project in a sustainable way it is expected that you donate to the project when opening a ticket,
if you're not a donor already. You can find donation options at https://floccus.org/donate/. Thank you!
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 Nextcloud 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 (Feb 5, 2025):
Hey @Presareo
I'm sorry for the delay. I sadly cannot reproduce this at the moment. Can you try this again with the latest version of floccus? URLs pointing to both existing and non-exisiting files were synced successfully and didn't cause the browser to go haywire.
@github-actions[bot] commented on GitHub (May 7, 2025):
Hello 👋
This issue appears to have had no activity for 3 months. We cannot keep track of whether individual issues
have resolved themselves or still require attention without user interaction. We're thus adding the stale label to this issue to schedule
it for getting closed in 5 days time. If you believe this issue is still valid and should be fixed, you can add a comment
or remove the label to avoid it getting closed.
Cheers 💙
@github-actions[bot] commented on GitHub (May 12, 2025):
This issue was closed because it has been stalled for 5 days with no activity.