starred/floccus

Fork 0

mirror of https://github.com/floccusaddon/floccus.git synced 2026-04-25 14:16:12 +03:00

[GH-ISSUE #2143] Synced tabs duplicating across browsers #1440

New issue

Open

opened 2026-02-25 22:40:01 +03:00 by kerem · 2 comments

kerem commented

2026-02-25 22:40:01 +03:00

Owner

Originally created by @erahhal on GitHub (Dec 31, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2143

Which version of floccus are you using?

v5.8.3

How many bookmarks do you have, roughly?

Are you using other means to sync bookmarks in parallel to floccus?

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.

Brave 1.85.117 (Official Build) (64-bit) Chromium: 143.0.7499.146

Which version of Nextcloud Bookmarks are you using? (if relevant)

16.0.1

Which version of Nextcloud? (if relevant)

32.0.3

What kind of WebDAV server are you using? (if relevant)

No response

Describe the Bug

I'm syncing tabs across 3 brave browsers. I've got pinned tabs, grouped tabs, and regular tabs. I've seen all of them duplicated, though I only saw groups duplicated ones. I see pinned tabs duplicated regularly, but they show up as unpinned. I think closing and opening the browser is triggering this. The pinned tabs are showing in a grey "unloaded" state when I first load the browser - not sure if this is related.

Expected Behavior

No duplication of tabs or groups.

To Reproduce

I haven't nailed down exact duplication steps, but it happens almost every time I close and open brave on one of the computers.

Debug log provided

I have provided a debug log file

Originally created by @erahhal on GitHub (Dec 31, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2143 ### Which version of floccus are you using? v5.8.3 ### How many bookmarks do you have, roughly? 60 ### Are you using other means to sync bookmarks in parallel to floccus? No ### 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. Brave 1.85.117 (Official Build) (64-bit) Chromium: 143.0.7499.146 ### Which version of Nextcloud Bookmarks are you using? (if relevant) 16.0.1 ### Which version of Nextcloud? (if relevant) 32.0.3 ### What kind of WebDAV server are you using? (if relevant) _No response_ ### Describe the Bug I'm syncing tabs across 3 brave browsers. I've got pinned tabs, grouped tabs, and regular tabs. I've seen all of them duplicated, though I only saw groups duplicated ones. I see pinned tabs duplicated regularly, but they show up as unpinned. I think closing and opening the browser is triggering this. The pinned tabs are showing in a grey "unloaded" state when I first load the browser - not sure if this is related. ### Expected Behavior No duplication of tabs or groups. ### To Reproduce I haven't nailed down exact duplication steps, but it happens almost every time I close and open brave on one of the computers. ### Debug log provided - [ ] I have provided a debug log file

kerem added the

bug

label

2026-02-25 22:40:01 +03:00

kerem commented

2026-02-25 22:40:01 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 31, 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. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings. I'm Marcel. I created floccus a few years ago, and have been maintaining it 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. It helps when you stick around to answer follow up questions I may have, as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report and the issue cannot be solved without it, I will have to close the issue after a while. Note also that GitHub in general 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! If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way, I ask that you donate to the project when opening an issue (or at least once your issue is solved), 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.

Thank you for reading through this primer. I look forward to working with you on this issue! Cheers! 💙

@github-actions[bot] commented on GitHub (Dec 31, 2025): Hello! :wave: 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. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings. I'm Marcel. I created floccus a few years ago, and have been maintaining it 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. It helps when you stick around to answer follow up questions I may have, as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report and the issue cannot be solved without it, I will have to close the issue after a while. Note also that GitHub in general 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! If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way, I ask that you donate to the project when opening an issue (or at least once your issue is solved), 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. Thank you for reading through this primer. I look forward to working with you on this issue! Cheers! :blue_heart:

kerem commented

2026-02-25 22:40:01 +03:00

Author

Owner

@TuringTestTwister commented on GitHub (Jan 1, 2026):

I think I might have identified when this happens. It's when the browser crashes or the computer locks up or turns off unexpectedly. When brave is re-opened, and the "recover last session" button is clicked is when this can be seen.

@TuringTestTwister commented on GitHub (Jan 1, 2026): I think I might have identified when this happens. It's when the browser crashes or the computer locks up or turns off unexpectedly. When brave is re-opened, and the "recover last session" button is clicked is when this can be seen.

kerem referenced this issue

2026-02-25 23:31:08 +03:00

[PR #1440] [CLOSED] build(deps-dev): bump browserify-sign from 4.2.1 to 4.2.2 #1885

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/floccus#1440

No description provided.

Rows
Columns