Runs indefinitely w/out syncing; no new logs created. #1196
-
Floccus Addon 4.15.0 For some time now, when I launch syncing in Floccus, the addon shows "Syncing" indefinitely but doesn't seem to be doing anything. Also, clicking "Cancel sync" does not stop the syncing. I've disabled Auto-sync and only manually launch a Push (upload local changes) from a single browser profile. Below are screenshots showing my settings. I've set up a single account/folder to sync. I can no longer see logs of recent actions because the buttons to download logs always show the following log from 5/23/22:
Nextcloud does not show any related errors. I figured it would help to troubleshoot before reporting these as issues. |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 13 replies
-
You should open an "issue" instead of a "discussion". I think it would be easier to follow the updates, etc.. 😃 |
Beta Was this translation helpful? Give feedback.
-
Does it help to disable and re-enable floccus? Usually, it should work again after 15min or so, if the account is locked on the server. See the faq on the topic:
|
Beta Was this translation helpful? Give feedback.
-
I did the following:
*Immediately after the sync started, Firefox complained that a running script was slowing it down. I had done nothing else in the browser. This didn't seem to affect my browsing during the hour. No change in behavior:
Before posting here, I even removed the account and added it anew. This made no difference. |
Beta Was this translation helpful? Give feedback.
-
I assume you know curl, based on your github profile. Using curl you can unlock nextcloud bookmarks manually:
|
Beta Was this translation helpful? Give feedback.
-
I've had time to try and reproduce this recently and could indeed replicate the bug. v4.16.0 should have the fix. Let me know if that works for you |
Beta Was this translation helpful? Give feedback.
-
Dear Developers and Community, Thank you very much for the project. Apparently, here's a similar issue (related to #972, probably):
On the client side: Table headers, respectively: What might it be? Best and kind regards |
Beta Was this translation helpful? Give feedback.
I've had time to try and reproduce this recently and could indeed replicate the bug. v4.16.0 should have the fix. Let me know if that works for you♥️