mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #1652] too many .xbel files created on Google Drive #1098
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#1098
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 @cimenta on GitHub (Jun 18, 2024).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1652
Which version of floccus are you using?
5.2.1
How many bookmarks do you have, roughly?
2000
Are you using other means to sync bookmarks in parallel to floccus?
no
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.
firefox, Brave, Chrome, Vivaldi
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
hi
on my Google Driver I got 88 floccus-bookmars.xbel files. They are created almost every day.
can you please have a look into it?
Thank you
Radek
Expected Behavior
just one .xbel file
To Reproduce
Not sure about the steps to reproduce. I installed floccus and have been using it. I do not think I did anything "special".
Sync between all 4 browsers I am using is working fine.
Debug log provided
@github-actions[bot] commented on GitHub (Jun 18, 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 💙
@marcelklehr commented on GitHub (Jun 20, 2024):
Hello Radek
That's a strange issue.
When did you start using Floccus with Google Drive and when did the second file appear?
@cimenta commented on GitHub (Jun 20, 2024):
hi Marcel
@cimenta commented on GitHub (Jun 20, 2024):
yes,
@marcelklehr commented on GitHub (Jul 2, 2024):
Do you use floccus also via the mobile app?
@cimenta commented on GitHub (Jul 2, 2024):
Never tried
Radek
On Tue, 2 July 2024, 19:31 Marcel Klehr, @.***> wrote:
@marcelklehr commented on GitHub (Jul 5, 2024):
What is your sync interval?
@marcelklehr commented on GitHub (Jul 5, 2024):
Can you try to identify one of the browsers that might be causing this, perhaps?
@marcelklehr commented on GitHub (Jul 5, 2024):
@teodias requests a cleaning routine for the excess xbel files
@marcelklehr commented on GitHub (Jul 6, 2024):
Which strategy are you syncing with?
@cimenta commented on GitHub (Jul 9, 2024):
now 5 mins but used to be the default 15 mins
I do not think it matters. it definitely started when it was 15. Continues when it is 5 mins
@cimenta commented on GitHub (Jul 9, 2024):
not sure how to identify ....
@cimenta commented on GitHub (Jul 9, 2024):
the settings are the same for all browsers. I imported them.
@marcelklehr commented on GitHub (Jul 18, 2024):
You can try disabling the extension on one of the browsers for a few days and see if that fixes it
@cimenta commented on GitHub (Jul 20, 2024):
ok, I stopped auto-sync for all browsers but Firefox ..
@cimenta commented on GitHub (Jul 22, 2024):
hi
so 2 days ago I disabled fluccus sync of all browses but firefox. And today I have new .xbel file on my Google drive.
@marcelklehr commented on GitHub (Jul 22, 2024):
Awesome, thank you for that. Can you try disabling firefox and enabling some other browser?
@cimenta commented on GitHub (Jul 22, 2024):
hi Marcel
I will update this ticket in a few days with my observations
Thank you
Radek
@cimenta commented on GitHub (Jul 28, 2024):
So after 6 days of using just Chrome it seems to me that everything is ok
Just the last .xbel is updated.
I am going to turn on syncing in firefox.
Radek
@marcelklehr commented on GitHub (Jul 28, 2024):
Interesting. So it seems firefox is the problem then. Or perhaps this was resolved with the latest update, that would be even better.
@namadori commented on GitHub (Jul 30, 2024):
I have the same issue, new files created randomly every few days or even multiple times a day.
I am using v5.2.5 on Chrome on Windows, Chrome on MacOs (but only in the weekend) and Android app. I was using Firefox but stopped some months ago.
I've been out of office for a week and no files were created, so I suspect that the Windows Chrome extension is making them.
I am still confused how Google Drive allows to have many files with the same name in the same folder. I noticed that the files are not created with the final name, but rather uploaded as "untitled", renamed and then edited a number of times, until a new file is created.
@marcelklehr commented on GitHub (Jul 30, 2024):
@namadori Anything after July 26 ? (That's when v5.2.5 was released, which might fix this)
@namadori commented on GitHub (Jul 30, 2024):
Too early to say, but maybe...
Couple of files on the 27th, then the PC was shut down during the weekend. The last 2 files created on the 27th are currently being updated, and no new files were created yesterday or today.
I'll look again in a couple of days, if will be no new files I think the issue is solved. Great timing :-)
@cimenta commented on GitHub (Jul 31, 2024):
nothing changed for me after I started to use firefox, I will wait for few more days and then introduce Vivaldi or Brave
@marcelklehr commented on GitHub (Aug 11, 2024):
Any news here? Did you get more excess files even with v5.2.5?
@cimenta commented on GitHub (Aug 11, 2024):
looks good to me
I am going to start using Brave
@namadori commented on GitHub (Aug 14, 2024):
The issue solved on Jul 27 for me, no more files created since then. Thanks for your support.
@ValuableIdeas commented on GitHub (Sep 9, 2024):
Hello,
I use Google Drive as sync method, and I have the same issue, which hasn't been resolved despite v5.2.5 at the end of July.
I'm currently using version 5.2.7 with Chrome (128.0.6613.120) and Firefox (130.0) on Windows, and the Android app v5.2.6 with Android 12.
I'm syncing two xbel files and they both have this problem.
@cimenta commented on GitHub (Sep 9, 2024):
I checked again... it looks like the issue was not solved. It is much better but I do have some duplicates. Not so many though
@marcelklehr commented on GitHub (Sep 10, 2024):
Could you check the history of the most recently updated file, to see if it's new or has been modified before?
@cimenta commented on GitHub (Sep 10, 2024):
and it starts like this
@ValuableIdeas commented on GitHub (Sep 10, 2024):
I have the same file history scheme as cimenta.
@marcelklehr commented on GitHub (Sep 12, 2024):
Aha, and what about the other files do they have multiple edits to them as well? I have a suspicion that when multiple files with the same name exist, the file to change is being picked at random, so in the upcoming release this is changed to always edit the last modified file with the name.
@ValuableIdeas commented on GitHub (Sep 12, 2024):
Yes, other files also have multiple edits.
In the history of each file, the first entry (‘you uploaded an item’) corresponds in date and time to the last modification of the previous file, so it's probably this one which has been uploaded and then modified.
@ChrisCh7 commented on GitHub (Oct 1, 2024):
Still happening after the most recent update.
There was a single xbel file, it updated it and at the same time it created a new file with the same name and continued to update that instead after that.
@marcelklehr commented on GitHub (Oct 9, 2024):
v5.3.1 is out now with a mechanism to at least remove all remnant xbel files, if we can't prevent them from being created. Let me know how it goes. :)
@ValuableIdeas commented on GitHub (Oct 9, 2024):
I updated and all the old files magically disappeared! Thanks a lot Marcel :)
@marcelklehr commented on GitHub (Oct 20, 2024):
Closing for now.
@github-actions[bot] commented on GitHub (Oct 21, 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.