[GH-ISSUE #643] Error: Trying to remove a non-existing ite

kerem commented

2026-02-25 22:37:06 +03:00

Owner

Originally created by @dilectia on GitHub (Aug 25, 2020).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/643

Describe the bug
I get this error in Firefox (not in Chrome with the same config)
Trying to remove a non-existing item from OrderTracker: folder:toolbar_____

To Reproduce
I just let flocus run... and get the error from the plugin icon

Expected behavior
Sync without errors XD

Screenshots

Desktop (please complete the following information):

Ubuntu Linux 18.04 LTS
Browser Firefox
Browser Version 79.0 (64-bit)
Floccus version: 4.3.0
Floccus sync method: nextcloud folders

Server (please complete the following information):

Ubuntu core 18.04
Nextcloud version: 19.0.1
Bookmarks app version: 3.3.3

Note: Please write down the actual version numbers instead of writing 'latest'.

Debug log
If you think it's relevant I'll provide it

Debug log provided

Additional context
I sync bookmarks with my toolbar bookmarks in firefox and chrome. I only get this error in Firefox...

Originally created by @dilectia on GitHub (Aug 25, 2020). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/643 **Describe the bug** I get this error in Firefox (not in Chrome with the same config) Trying to remove a non-existing item from OrderTracker: folder:toolbar_____ **To Reproduce** I just let flocus run... and get the error from the plugin icon **Expected behavior** Sync without errors XD **Screenshots** **Desktop (please complete the following information):** - Ubuntu Linux 18.04 LTS - Browser Firefox - Browser Version 79.0 (64-bit) - Floccus version: 4.3.0 - Floccus sync method: nextcloud folders **Server (please complete the following information):** - Ubuntu core 18.04 - Nextcloud version: 19.0.1 - Bookmarks app version: 3.3.3 Note: Please write down the actual version numbers instead of writing 'latest'. **Debug log** If you think it's relevant I'll provide it - [ ] Debug log provided **Additional context** I sync bookmarks with my toolbar bookmarks in firefox and chrome. I only get this error in Firefox...

kerem

2026-02-25 22:37:06 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 22:37:06 +03:00

Author

Owner

@brainchild0 commented on GitHub (Aug 25, 2020):

Also affected, using same browser configuration and extension version, under Linux Mint 20.0.

(Same problem appeared with 4.2.0. I had hoped that the update would resolve it.)

Trying to insert an already existing item into OrderTracker: bookmark:XXXXXX

@brainchild0 commented on GitHub (Aug 25, 2020): Also affected, using same browser configuration and extension version, under Linux Mint 20.0. (Same problem appeared with 4.2.0. I had hoped that the update would resolve it.) --- ``` Trying to insert an already existing item into OrderTracker: bookmark:XXXXXX ```

kerem commented

2026-02-25 22:37:06 +03:00

Author

Owner

@marcelklehr commented on GitHub (Aug 25, 2020):

I get this error in Firefox (not in Chrome with the same config)

That's curious.

I had hoped that update would resolve it.

So had I :/

I'll look into this.

@marcelklehr commented on GitHub (Aug 25, 2020): > I get this error in Firefox (not in Chrome with the same config) That's curious. > I had hoped that update would resolve it. So had I :/ I'll look into this.

kerem commented

2026-02-25 22:37:06 +03:00

Author

Owner

@sleepinghua commented on GitHub (Aug 30, 2020):

Same problem:

"Trying to remove a non-existing item from OrderTracker: bookmark:1820\nTrying to remove a non-existing item from OrderTracker: folder:2219"

windows 19041.450
chrome 85.0.4183.83 x64
Floccus version: 4.3.0
Floccus sync method: WebDAV

@sleepinghua commented on GitHub (Aug 30, 2020): Same problem: **"Trying to remove a non-existing item from OrderTracker: bookmark:1820\nTrying to remove a non-existing item from OrderTracker: folder:2219"** - windows 19041.450 - chrome 85.0.4183.83 x64 - Floccus version: 4.3.0 - Floccus sync method: WebDAV

kerem commented

2026-02-25 22:37:06 +03:00

Author

Owner

@marcelklehr commented on GitHub (Sep 1, 2020):

Good news: I've been able to reproduce this error with fuzzy testing. Now I just need to find the cause :)

@marcelklehr commented on GitHub (Sep 1, 2020): Good news: I've been able to [reproduce this error with fuzzy testing](https://github.com/marcelklehr/floccus/runs/1056456345). Now I just need to find the cause :)

kerem commented

2026-02-25 22:37:06 +03:00

Author

Owner

@dilectia commented on GitHub (Sep 1, 2020):

It probably doesn't add any info, but suddenly it works fine... I don't think I have done anything...

@dilectia commented on GitHub (Sep 1, 2020): It probably doesn't add any info, but suddenly it works fine... I don't think I have done anything...

kerem commented

2026-02-25 22:37:06 +03:00

Author

Owner

@brainchild0 commented on GitHub (Sep 1, 2020):

Following @dilectia's observation, I noticed that the upgrade from Firefox 79.0 to 80.0 appears to resolve the issue.

@brainchild0 commented on GitHub (Sep 1, 2020): Following @dilectia's observation, I noticed that the upgrade from Firefox 79.0 to 80.0 appears to resolve the issue.

kerem commented

2026-02-25 22:37:06 +03:00

Author

Owner

@brainchild0 commented on GitHub (Sep 1, 2020):

Also, probably OT, but after the error occurred, I noticed that the extension ignored requests to restart the synchronization operation. Only restarting the entire browser would make it possible to start a new operation.

@brainchild0 commented on GitHub (Sep 1, 2020): Also, probably OT, but after the error occurred, I noticed that the extension ignored requests to restart the synchronization operation. Only restarting the entire browser would make it possible to start a new operation.

kerem commented

2026-02-25 22:37:06 +03:00

Author

Owner

@marcelklehr commented on GitHub (Sep 18, 2020):

Thanks for all your feedback, folks! I'm currently working on a new iteration of the sync algorithm that should fix this: #651

@marcelklehr commented on GitHub (Sep 18, 2020): Thanks for all your feedback, folks! I'm currently working on a new iteration of the sync algorithm that should fix this: #651

kerem commented

2026-02-25 22:37:06 +03:00

Author

Owner

@marcelklehr commented on GitHub (Oct 5, 2020):

I've since rewritten the sync algorithm to avoid this kind of problems. Head over to https://github.com/marcelklehr/floccus/issues/666 if you'd like to help test the new version.

@marcelklehr commented on GitHub (Oct 5, 2020): I've since rewritten the sync algorithm to avoid this kind of problems. Head over to https://github.com/marcelklehr/floccus/issues/666 if you'd like to help test the new version.

kerem commented

2026-02-25 22:37:06 +03:00

Author

Owner

@marcelklehr commented on GitHub (Oct 12, 2020):

I'd be very grateful if you could try out the release candidate: #666 -- I promise, you'll get extra cookies :) ❤️

@marcelklehr commented on GitHub (Oct 12, 2020): I'd be very grateful if you could try out the release candidate: #666 -- I promise, you'll get extra cookies :) :heart:

kerem commented

2026-02-25 22:37:06 +03:00

Author

Owner

@brainchild0 commented on GitHub (Oct 12, 2020):

The problem, at least for me, is that such a test would offer no new information, unless under the earlier version of Firefox, because the problem resolved in recent versions. Isolating the issue would depend on replicating the environment in which it appeared. (See previous comment.)

@brainchild0 commented on GitHub (Oct 12, 2020): The problem, at least for me, is that such a test would offer no new information, unless under the earlier version of Firefox, because the problem resolved in recent versions. Isolating the issue would depend on replicating the environment in which it appeared. (See previous comment.)

kerem commented

2026-02-25 22:37:06 +03:00

Author

Owner

@marcelklehr commented on GitHub (Oct 12, 2020):

I see. Since OP hasn't responded in a while I'm gonna close this. Please shout if you do continue to experience this :)

@marcelklehr commented on GitHub (Oct 12, 2020): I see. Since OP hasn't responded in a while I'm gonna close this. Please shout if you do continue to experience this :)

kerem commented

2026-02-25 22:37:06 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 21, 2023):

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 21, 2023): 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.

Rows
Columns

[GH-ISSUE #643] Error: Trying to remove a non-existing ite #425