starred/floccus

Fork 0

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

[GH-ISSUE #1566] Bookmarks destroyed, backups can't be loaded #1034

New issue

Closed

opened 2026-02-25 22:38:47 +03:00 by kerem · 8 comments

kerem commented

2026-02-25 22:38:47 +03:00

Owner

Originally created by @timcurran on GitHub (Mar 19, 2024).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1566

Which version of floccus are you using?

5.0.10

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.

Edge Version 122.0.2365.92 (Official build) (64-bit)

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

Today I found that my bookmark order was suddenly scrambled, with at least one critical folder missing. First move was to go to a backup (i.e. a previous version stored by Google Drive).

None of the previous ten versions would load (except a couple of the most recent, which all had the same missing/scrambled folders). Instead of loading, they created Google Drive files with the same exact name, only much, much smaller (e.g. 130KB vs 450 bytes) and no bookmarks at all.

I finally tried a month-old stored backup which happens to be unencrypted (i.e. a pure, human-readable XML version of the XBEL file). In order to load it, I removed the passphrase. Now I get the error "E034: Remote bookmarks file is unreadable. Did you forget to set an encryption passphrase? Last synchronized: 2 hours ago" In other words, Floccus won't load an unencrypted version of its own file format. Something is obviously very wrong.

What can I do to recover my bookmarks?

Expected Behavior

Floccus to sync all bookmarks in order and load previous files that have the same passphrase.

To Reproduce

Load a previous version of bookmarks.xbel to Google Drive (I suspect to reproduce, you'll have to use an xbel created under a previous version of Floccus). Give it a slightly different name (e.g. bookmarks-1.xbel).
Change the filename in the "Server Details" setting tab to match.
Attempt a Pull Down Once sync.
All your bookmarks will suddenly disappear and there will be an empty duplicate-name file on Google Drive.
Follow the same steps with a passphrase-free (unencrypted xbel). Intead of the duplicate file, you'll get ....
Debug log will say something like this:

2024-03-19T23:15:40.599Z Starting sync process for account Google Drive: bookmarks 2-11-24.xbel
2024-03-19T23:15:40.603Z onSyncStart: begin
2024-03-19T23:15:41.454Z Syncing failed with E034: Remote bookmarks file is unreadable. Did you forget to set an encryption passphrase?
2024-03-19T23:15:41.463Z onSyncFail

Debug log provided

I have provided a debug log file

Originally created by @timcurran on GitHub (Mar 19, 2024). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1566 ### Which version of floccus are you using? 5.0.10 ### 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. Edge Version 122.0.2365.92 (Official build) (64-bit) ### 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 Today I found that my bookmark order was suddenly scrambled, with at least one critical folder missing. First move was to go to a backup (i.e. a previous version stored by Google Drive). None of the previous ten versions would load (except a couple of the most recent, which all had the same missing/scrambled folders). Instead of loading, they created Google Drive files with the same exact name, only much, much smaller (e.g. 130KB vs 450 bytes) and no bookmarks at all. I finally tried a month-old stored backup which happens to be unencrypted (i.e. a pure, human-readable XML version of the XBEL file). In order to load it, I removed the passphrase. Now I get the error "E034: Remote bookmarks file is unreadable. Did you forget to set an encryption passphrase? Last synchronized: 2 hours ago" In other words, Floccus won't load an *unencrypted* version of its own file format. Something is obviously very wrong. What can I do to recover my bookmarks? ### Expected Behavior Floccus to sync all bookmarks in order and load previous files that have the same passphrase. ### To Reproduce 1. Load a previous version of bookmarks.xbel to Google Drive (I suspect to reproduce, you'll have to use an xbel created under a *previous version* of Floccus). Give it a slightly different name (e.g. bookmarks-1.xbel). 2. Change the filename in the "Server Details" setting tab to match. 3. Attempt a Pull Down Once sync. 4. All your bookmarks will suddenly disappear and there will be an empty duplicate-name file on Google Drive. 5. Follow the same steps with a passphrase-free (unencrypted xbel). Intead of the duplicate file, you'll get .... 6. Debug log will say something like this: `2024-03-19T23:15:40.599Z Starting sync process for account Google Drive: bookmarks 2-11-24.xbel` `2024-03-19T23:15:40.603Z onSyncStart: begin` `2024-03-19T23:15:41.454Z Syncing failed with E034: Remote bookmarks file is unreadable. Did you forget to set an encryption passphrase?` `2024-03-19T23:15:41.463Z onSyncFail` ### Debug log provided - [ ] I have provided a debug log file

kerem

2026-02-25 22:38:47 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 22:38:47 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 19, 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 💙

@github-actions[bot] commented on GitHub (Mar 19, 2024): 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. 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 :blue_heart:

kerem commented

2026-02-25 22:38:47 +03:00

Author

Owner

@marcelklehr commented on GitHub (Mar 20, 2024):

Hi,

floccus cannot read arbitrary files on your Drive, but only files it created itself. So, you will have to copy the contents of one of your backup files into a file created by floccus.

@marcelklehr commented on GitHub (Mar 20, 2024): Hi, floccus cannot read arbitrary files on your Drive, but only files it created itself. So, you will have to copy the contents of one of your backup files into a file created by floccus.

kerem commented

2026-02-25 22:38:47 +03:00

Author

Owner

@timcurran commented on GitHub (Mar 20, 2024):

Sorry if I wasn't clear. The file I refer to IS a floccus-created xbel
file. It's just unencrypted.

Tim Curran
Home/Cell 917-208-5321
email: @.***
web: www.timcurran.com
LinkedIn: linkedin.com/in/currannews/
Skype (Video): tacurran

Message sent from my Samsung Android. Damn you, autocorrect!

On Wed, Mar 20, 2024, 7:38 AM Marcel Klehr @.***> wrote:

Hi,

floccus cannot read arbitrary files on your Drive, but only files it
created itself. So, you will have to copy the contents of one of your
backup files into a file created by floccus.

—
Reply to this email directly, view it on GitHub
https://github.com/floccusaddon/floccus/issues/1566#issuecomment-2009368886,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA6GO54KA6EFKLREWNV2E3TYZFYMPAVCNFSM6AAAAABE6QAFUSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBZGM3DQOBYGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

@timcurran commented on GitHub (Mar 20, 2024): Sorry if I wasn't clear. The file I refer to IS a floccus-created xbel file. It's just unencrypted. ---- Tim Curran Home/Cell 917-208-5321 email: ***@***.*** web: www.timcurran.com LinkedIn: linkedin.com/in/currannews/ Skype (Video): tacurran Message sent from my Samsung Android. Damn you, autocorrect! On Wed, Mar 20, 2024, 7:38 AM Marcel Klehr ***@***.***> wrote: > Hi, > > floccus cannot read arbitrary files on your Drive, but only files it > created itself. So, you will have to copy the contents of one of your > backup files into a file created by floccus. > > — > Reply to this email directly, view it on GitHub > <https://github.com/floccusaddon/floccus/issues/1566#issuecomment-2009368886>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AA6GO54KA6EFKLREWNV2E3TYZFYMPAVCNFSM6AAAAABE6QAFUSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBZGM3DQOBYGY> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

kerem commented

2026-02-25 22:38:47 +03:00

Author

Owner

@timcurran commented on GitHub (Mar 20, 2024):

I've attached the file I was referring to.

bookmarks 2-11-24.xbel
https://drive.google.com/file/d/1clrFmx5xoZuRnGemaWwnn2DHpKA42jRB/view?usp=drivesdk

Tim Curran
Home/Cell 917-208-5321
email: @.***
web: www.timcurran.com
LinkedIn: linkedin.com/in/currannews/
Skype (Video): tacurran

Message sent from my Samsung Android. Damn you, autocorrect!

On Wed, Mar 20, 2024, 7:43 AM Tim Curran @.***> wrote:

Sorry if I wasn't clear. The file I refer to IS a floccus-created xbel
file. It's just unencrypted.

Tim Curran
Home/Cell 917-208-5321
email: @.***
web: www.timcurran.com
LinkedIn: linkedin.com/in/currannews/
Skype (Video): tacurran

Message sent from my Samsung Android. Damn you, autocorrect!

On Wed, Mar 20, 2024, 7:38 AM Marcel Klehr @.***>
wrote:

Hi,

floccus cannot read arbitrary files on your Drive, but only files it
created itself. So, you will have to copy the contents of one of your
backup files into a file created by floccus.

—
Reply to this email directly, view it on GitHub
https://github.com/floccusaddon/floccus/issues/1566#issuecomment-2009368886,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA6GO54KA6EFKLREWNV2E3TYZFYMPAVCNFSM6AAAAABE6QAFUSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBZGM3DQOBYGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

@timcurran commented on GitHub (Mar 20, 2024): I've attached the file I was referring to. bookmarks 2-11-24.xbel <https://drive.google.com/file/d/1clrFmx5xoZuRnGemaWwnn2DHpKA42jRB/view?usp=drivesdk> ---- Tim Curran Home/Cell 917-208-5321 email: ***@***.*** web: www.timcurran.com LinkedIn: linkedin.com/in/currannews/ Skype (Video): tacurran Message sent from my Samsung Android. Damn you, autocorrect! On Wed, Mar 20, 2024, 7:43 AM Tim Curran ***@***.***> wrote: > Sorry if I wasn't clear. The file I refer to IS a floccus-created xbel > file. It's just unencrypted. > > ---- > Tim Curran > Home/Cell 917-208-5321 > email: ***@***.*** > web: www.timcurran.com > LinkedIn: linkedin.com/in/currannews/ > Skype (Video): tacurran > > Message sent from my Samsung Android. Damn you, autocorrect! > > > On Wed, Mar 20, 2024, 7:38 AM Marcel Klehr ***@***.***> > wrote: > >> Hi, >> >> floccus cannot read arbitrary files on your Drive, but only files it >> created itself. So, you will have to copy the contents of one of your >> backup files into a file created by floccus. >> >> — >> Reply to this email directly, view it on GitHub >> <https://github.com/floccusaddon/floccus/issues/1566#issuecomment-2009368886>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AA6GO54KA6EFKLREWNV2E3TYZFYMPAVCNFSM6AAAAABE6QAFUSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBZGM3DQOBYGY> >> . >> You are receiving this because you authored the thread.Message ID: >> ***@***.***> >> >

kerem commented

2026-02-25 22:38:47 +03:00

Author

Owner

@marcelklehr commented on GitHub (Mar 20, 2024):

IS a floccus-created xbel

The contents may be produced by floccus, but reading your steps to reproduce the file was created by you, not as a result of syncing with floccus, this is what I'm referring to.

So, I would recommend the following steps to recover:

Load a previous version of bookmarks.xbel to Google Drive. Instead of giving it a different name or somesuch, copy the old file contents into the current bookmarks.xbel that is synced by floccus. The old floccus file will need to be encrypted just like the current file.
Do not change the file name in the server details settings
Attempt a Pull Down Once sync

If you only have unencrypted backups, you will need to disable encryption in floccus before following the steps.

@marcelklehr commented on GitHub (Mar 20, 2024): > IS a floccus-created xbel The contents may be produced by floccus, but reading your steps to reproduce the file was created by you, not as a result of syncing with floccus, this is what I'm referring to. So, I would recommend the following steps to recover: 1. Load a previous version of bookmarks.xbel to Google Drive. Instead of giving it a different name or somesuch, copy the old file contents into the current bookmarks.xbel that is synced by floccus. The old floccus file will need to be encrypted just like the current file. 2. Do not change the file name in the server details settings 3. Attempt a Pull Down Once sync If you only have unencrypted backups, you will need to disable encryption in floccus before following the steps.

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@timcurran commented on GitHub (Mar 21, 2024):

After my initial report, I discovered that the Floccus app on my phone had
a relatively recent copy of the bookmarks. And, as a bonus, the app permits
exporting an html bookmark file. So was able to reconstruct my bookmarks.

I was mainly trying to report a possible bug. But if you haven't received
any other similar reports, it may just be a fluke with my setup.

Thanks for your help.

Tim Curran
Home/Cell 917-208-5321 *
email: @.* @.**>
web: www.timcurran.com http://www.timcurran.com
LinkedIn: linkedin.com/in/currannews/
http://www.linkedin.com/in/currannews/
Skype (Video): tacurran

(IF TEXT IS IN ALL CAPS, I'M NOT YELLING. IT'S BECAUSE THAT IS HOW WE ROLL
WHEN SCRIPTING TV NEWS)

On Wed, Mar 20, 2024 at 8:07 AM Marcel Klehr @.***>
wrote:

So, I would recommend the following steps to recover:

Load a previous version of bookmarks.xbel to Google Drive. Instead
of giving it a different name or somesuch, copy the old file contents into
the current bookmarks.xbel that is synced by floccus. The old floccus file
will need to be encrypted just like the current file.

Do not change the file name in the server details settings

Attempt a Pull Down Once sync

If you only have unencrypted backups, you will need to disable encryption
in floccus before following the steps.

—
Reply to this email directly, view it on GitHub
https://github.com/floccusaddon/floccus/issues/1566#issuecomment-2009415549,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA6GO544SMCVFMGMSDQSEULYZF3XLAVCNFSM6AAAAABE6QAFUSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBZGQYTKNJUHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

@timcurran commented on GitHub (Mar 21, 2024): After my initial report, I discovered that the Floccus app on my phone had a relatively recent copy of the bookmarks. And, as a bonus, the app permits exporting an html bookmark file. So was able to reconstruct my bookmarks. I was mainly trying to report a possible bug. But if you haven't received any other similar reports, it may just be a fluke with my setup. Thanks for your help. *Tim Curran* *Home/Cell 917-208-5321 * *email: ***@***.*** ***@***.***>* *web: www.timcurran.com <http://www.timcurran.com>* *LinkedIn: linkedin.com/in/currannews/ <http://www.linkedin.com/in/currannews/>* *Skype (Video): tacurran* (IF TEXT IS IN ALL CAPS, I'M NOT YELLING. IT'S BECAUSE THAT IS HOW WE ROLL WHEN SCRIPTING TV NEWS) On Wed, Mar 20, 2024 at 8:07 AM Marcel Klehr ***@***.***> wrote: > So, I would recommend the following steps to recover: > > 1. Load a previous version of bookmarks.xbel to Google Drive. Instead > of giving it a different name or somesuch, copy the old file contents into > the current bookmarks.xbel that is synced by floccus. The old floccus file > will need to be encrypted just like the current file. > 2. Do not change the file name in the server details settings > 3. Attempt a Pull Down Once sync > > If you only have unencrypted backups, you will need to disable encryption > in floccus before following the steps. > > — > Reply to this email directly, view it on GitHub > <https://github.com/floccusaddon/floccus/issues/1566#issuecomment-2009415549>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AA6GO544SMCVFMGMSDQSEULYZF3XLAVCNFSM6AAAAABE6QAFUSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBZGQYTKNJUHE> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@marcelklehr commented on GitHub (Mar 21, 2024):

Ah, that's great. Closing

@marcelklehr commented on GitHub (Mar 21, 2024): Ah, that's great. Closing

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 22, 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.

@github-actions[bot] commented on GitHub (Mar 22, 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.

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#1034

No description provided.

Rows
Columns