starred/floccus

Fork 0

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

[GH-ISSUE #2125] ENOENT Error When Setting Up Sync Over Git #1424

New issue

Open

opened 2026-02-25 22:39:58 +03:00 by kerem · 8 comments

kerem commented

2026-02-25 22:39:58 +03:00

Owner

Originally created by @balthanon on GitHub (Dec 14, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2125

Which version of floccus are you using?

5.8.2

How many bookmarks do you have, roughly?

3000

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

Sync method

Git

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

Floorp 12.8.3@146.0 (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

When I was setting up syncing over Git I ran across an issue where it gave me the error: ENOENT: /84b00aebc6031cdecf5edd61a94d35a58c1c47df36440a9f0bcec3f55a81dc5a1765729375211/bookmark-menu | Last synchronized: 0 seconds ago

I was able to troubleshoot this by looking up the error in a general Git context and it turned out that I didn't have Git in my Path variables. While it's likely someone else will be able to troubleshoot the same way potentially, I thought I would document the issue so that it's available here if someone encounters it and starts with Github rather than a search engine.

One particular caveat to this for Floccus specifically is that fixing the issue in the addon required not just adding the path to Git into the Path variables and restarting the browser, I also had to remove the profile I was syncing and recreate it. I'm not sure if this is a caching issue for Floccus or something on the browser side-- it's possible that this is worth looking into, but I primarily opened this issue just so that it was present in the issue list as mentioned above. So it can probably be closed immediately unless someone else wants to add some additional context.

Expected Behavior

Syncing normally without an error message.

To Reproduce

Remove Git paths from your Path variable and try syncing a Git based profile.

Debug log provided

I have provided a debug log file

Originally created by @balthanon on GitHub (Dec 14, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2125 ### Which version of floccus are you using? 5.8.2 ### How many bookmarks do you have, roughly? 3000 ### Are you using other means to sync bookmarks in parallel to floccus? No ### Sync method Git ### Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please. Floorp 12.8.3@146.0 (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 When I was setting up syncing over Git I ran across an issue where it gave me the error: ENOENT: /84b00aebc6031cdecf5edd61a94d35a58c1c47df36440a9f0bcec3f55a81dc5a1765729375211/bookmark-menu | Last synchronized: 0 seconds ago I was able to troubleshoot this by looking up the error in a general Git context and it turned out that I didn't have Git in my Path variables. While it's likely someone else will be able to troubleshoot the same way potentially, I thought I would document the issue so that it's available here if someone encounters it and starts with Github rather than a search engine. One particular caveat to this for Floccus specifically is that fixing the issue in the addon required not just adding the path to Git into the Path variables and restarting the browser, I also had to remove the profile I was syncing and recreate it. I'm not sure if this is a caching issue for Floccus or something on the browser side-- it's possible that this is worth looking into, but I primarily opened this issue just so that it was present in the issue list as mentioned above. So it can probably be closed immediately unless someone else wants to add some additional context. ### Expected Behavior Syncing normally without an error message. ### To Reproduce Remove Git paths from your Path variable and try syncing a Git based profile. ### Debug log provided - [ ] I have provided a debug log file

kerem added the

bug

label

2026-02-25 22:39:58 +03:00

kerem commented

2026-02-25 22:39:59 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 14, 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 14, 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:39:59 +03:00

Author

Owner

@balthanon commented on GitHub (Dec 14, 2025):

As noted, primarily adding this for consistency sake-- I am going to add another feature request I think to update the FAQ/installation instructions for the website too. I ran into the 401 error that required creating a PAT for Github despite not having 2-factor authentication setup and this, and it would be good to include both of those for people getting set to use this method.

If those are available on Git, I can probably just submit a pull request directly-- haven't checked.

@balthanon commented on GitHub (Dec 14, 2025): As noted, primarily adding this for consistency sake-- I am going to add another feature request I think to update the FAQ/installation instructions for the website too. I ran into the 401 error that required creating a PAT for Github despite not having 2-factor authentication setup and this, and it would be good to include both of those for people getting set to use this method. If those are available on Git, I can probably just submit a pull request directly-- haven't checked.

kerem commented

2026-02-25 22:39:59 +03:00

Author

Owner

@marcelklehr commented on GitHub (Dec 20, 2025):

One particular caveat to this for Floccus specifically is that fixing the issue in the addon required not just adding the path to Git into the Path variables and restarting the browser, I also had to remove the profile I was syncing and recreate it.

You definitely do not need git installed on your machine to use foccus with git. 🤔

I also had to remove the profile I was syncing and recreate it.

This is likely what fixed the issue ;)

@marcelklehr commented on GitHub (Dec 20, 2025): > One particular caveat to this for Floccus specifically is that fixing the issue in the addon required not just adding the path to Git into the Path variables and restarting the browser, I also had to remove the profile I was syncing and recreate it. You definitely do not need git installed on your machine to use foccus with git. 🤔 > I also had to remove the profile I was syncing and recreate it. This is likely what fixed the issue ;)

kerem commented

2026-02-25 22:39:59 +03:00

Author

Owner

@balthanon commented on GitHub (Dec 20, 2025):

This is likely what fixed the issue ;)

Hmm... this was a brand new profile already that I created specifically for testing Git. Could the fact that I did have Git installed have caused it-- made it look to my installation rather than ignoring it or something? If you don't need it, I'm not sure what would trigger the ENOENT issue specifically, since it presumably shouldn't be checking for anything on the file system at all.

I might have messed up the URL initially as well and corrected it, so if it cached something that might be another area. Probably not a good method of troubleshooting unless I can replicate this though.

@balthanon commented on GitHub (Dec 20, 2025): > This is likely what fixed the issue ;) Hmm... this was a brand new profile already that I created specifically for testing Git. Could the fact that I did have Git installed have caused it-- made it look to my installation rather than ignoring it or something? If you don't need it, I'm not sure what would trigger the ENOENT issue specifically, since it presumably shouldn't be checking for anything on the file system at all. I might have messed up the URL initially as well and corrected it, so if it cached something that might be another area. Probably not a good method of troubleshooting unless I can replicate this though.

kerem commented

2026-02-25 22:39:59 +03:00

Author

Owner

@marcelklehr commented on GitHub (Dec 20, 2025):

since it presumably shouldn't be checking for anything on the file system at all.

Floccus uses an internal file system for the git sync method

@marcelklehr commented on GitHub (Dec 20, 2025): > since it presumably shouldn't be checking for anything on the file system at all. Floccus uses an internal file system for the git sync method

kerem commented

2026-02-25 22:39:59 +03:00

Author

Owner

@marcelklehr commented on GitHub (Dec 20, 2025):

I might have messed up the URL initially as well and corrected it, so if it cached something that might be another area. Probably not a good method of troubleshooting unless I can replicate this though.

mmh, I can try to reproduce this

@marcelklehr commented on GitHub (Dec 20, 2025): > I might have messed up the URL initially as well and corrected it, so if it cached something that might be another area. Probably not a good method of troubleshooting unless I can replicate this though. mmh, I can try to reproduce this

kerem commented

2026-02-25 22:39:59 +03:00

Author

Owner

@PaulDevenney commented on GitHub (Dec 21, 2025):

As noted, primarily adding this for consistency sake-- I am going to add another feature request I think to update the FAQ/installation instructions for the website too. I ran into the 401 error that required creating a PAT for Github despite not having 2-factor authentication setup and this, and it would be good to include both of those for people getting set to use this method.

If those are available on Git, I can probably just submit a pull request directly-- haven't checked.

This comment saved me. For quick reference if you are updating the docs (or just see this comment relating to 401 errors syncing to GH

Github | Settings | Developer Settings | Personal Access Tokens | Fine-grained tokens
Generate New Token
Expiration - make sure you are aware if its not set to "never", as you will need to regularly fix your floccus extension config
Only Select Repositories | Chose your Floccus repo
Permissions | Add Permissions | Contents | Read and Write
Generate Token
Remember to store it somewhere as you will need it for each browser extension you are syncing from!

@PaulDevenney commented on GitHub (Dec 21, 2025): > As noted, primarily adding this for consistency sake-- I am going to add another feature request I think to update the FAQ/installation instructions for the website too. I ran into the 401 error that required creating a PAT for Github despite not having 2-factor authentication setup and this, and it would be good to include both of those for people getting set to use this method. > > If those are available on Git, I can probably just submit a pull request directly-- haven't checked. This comment saved me. For quick reference if you are updating the docs (or just see this comment relating to 401 errors syncing to GH 1. Github | Settings | Developer Settings | Personal Access Tokens | Fine-grained tokens 2. Generate New Token 3. Expiration - make sure you are aware if its not set to "never", as you will need to regularly fix your floccus extension config 4. Only Select Repositories | Chose your Floccus repo 5. Permissions | Add Permissions | Contents | Read and Write 6. Generate Token 7. Remember to store it somewhere as you will need it for each browser extension you are syncing from!

kerem commented

2026-02-25 22:39:59 +03:00

Author

Owner

@balthanon commented on GitHub (Dec 23, 2025):

I just submitted a pull request to include some references to this in the website documentation; I didn't include specific Github navigation, but it might not be a bad idea given that it's probably the most common git instance that someone might use.

@balthanon commented on GitHub (Dec 23, 2025): I just submitted a pull request to include some references to this in the website documentation; I didn't include specific Github navigation, but it might not be a bad idea given that it's probably the most common git instance that someone might use.

kerem referenced this issue

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

[PR #1487] [MERGED] Android App Launcher Icon Improvements #1895

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

No description provided.

Rows
Columns