client versions: 1.0.195 (desktop, linux), 1.0.324 (android) OS: Ubuntu Linux 19.10 x86_64 Since some days ago I was having issues with a locked file on my nextcloud provider, I choosed to start over in another folder: so I downloaded via web browser old folder and reuploaded it in another one using nextcloud client (too many files to handle with web ui), after that I started to switch folder into clients configuration and disable encryption (I was having also encryption issues), since then, apart of mine android client that performed successfully a complete sync, desktop clients keeps writing over and over again remote files which don’t produce any local file change in any of connected clients. In console I didn’t found nothing but I have some lines in log.txt telling something about synchronization action, which I attach.log.txt (312.1 KB) To make this long first sync I choose to run joplin at the same time in both desktops, could be this the problem source? Maybe their trying to write and rewrite over and over again same files?

What does uname -a produce? Please paste the terminal output here. Thanks

yes, it is $ uname -a Linux pavilion 5.3.0-42-generic #34-Ubuntu SMP Fri Feb 28 05:49:40 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux on both systems

Good deal. It’s not the 5.5 bug. Can you try something crazy, though? I wanna see if maybe this fix fixes other issues here on Linux mostly. [image] Joplin Freezing on Linux Distros Running Kernel 5.5 Bug Update Support One of the people helping me with this bug found a quick and easy way to get around it: Whenever Joplin Freezes during sync, go to Options=>Tools Click the WebClipper tab up top Enable and then Disable Webclipper Click Apply Go back to business as usual. smiley Here's a demo:

Mine sync doesn’t freeze, it goes on and on forever, anyway I’ll try the solution posted and let you know how it goes.

I completely understand. I’m asking because that solution linked shouldn’t fix the issue it does but does for the time being and may do something for you. Your log shows the same error that pops up when the 5.5 bug happens.

I tried the procedure shown in video you posted but nothing seems to change. In options -> web clipper I enabled and disabled service.

Any other suggestion? A safe way to start over without losing data and possibly fix this issue? Any other suggestion that would fix this? Do you need further information to better diagnose the problem?

I don’t have other suggestions right now that are fixes but the more information you can give that’s very specific, including possible video or gifs of what’s happening, the better others can help you.

do you mean I need to show a gif or a video where the count of remotely updated elements slowly increases over and over again ? This is what happen everytime I launch Joplin and wait to begin sync , or I start it clicking the button. I think that is nothing interesting, the application seems going well, synchronizing elements and giving no errors.

Syncing forever

Support

bedwardly-down 24 March 2020 19:10 4

Good deal. It’s not the 5.5 bug. Can you try something crazy, though? I wanna see if maybe this fix fixes other issues here on Linux mostly.

Topic		Replies	Views
Cannot Aquire Sync Lock Support	33	11700	13 June 2025
Can't sync from android to desktop after fresh install Support	7	1132	14 January 2022
Joplin won't sync on Debian Support	5	720	15 October 2019
With Encryption on, even with local file system sync, Joplin locks up for seconds Support	0	52	17 September 2026
Sometimes latest changes get reverted (during sync?) Support	22	2804	21 April 2020

Syncing forever

Related topics