This is a error from Nextcloud, the file Joplin/info.json is locked in Nextcloud from a other session or a session that no longer exists, but nextcloud has not released the lock.
If you search for FileLocked on the forum there are many threads about this. It's indeed a bug in Nextcloud (that they'll apparently never fix), and you need to use Redis for file locking to prevent this.
No, they are talking rubbish. I was originally using tab.digital and moved away because I was having horrendous locking issues and decided to host my own nextcloud instead.
What they are referring to is the old (deprecated) joplin nextcloud app which has been entirely replaced in functionality by Joplin Cloud/Server. It has nothing to do with the desktop app.
Edit, from my support ticket:
Hello,
Unfortunately the Joplin app is not supported since Nextcloud version 18
Hi,
Where is that compatibility information from? I know that the deprecated Joplin Nextcloud service isn't supported but the main Joplin app has been working just fine on Nextcloud 20 and as far as I'm aware there aren't any active nextcloud incompatibilities with the latest versions of Joplin
Sorry, we were referring to the Joplin app in Nextcloud, which is not what you're using.
Are you able to upload any files to the Joplin folder, or does only syncing with Joplin cause issues?
Yes that's not true. Plenty of people have no problem synchronising with Nextcloud. They have a misconfigured server and either don't want to admit it or just don't realise it. This error doesn't happen with Redis normally, unless they have a weird setup with async replication or something like this.