This issue has been constant and on every version of Nextcloud since v12 till now the latest v13.0.2.
Even thou I am the only user, every time I was working on any file, I would 80% of the time get a conflict.
My set-up is as follows:
- Raspberry Pi 3
- Raspbian v9.4
- MariaDB v10.1.23
- nginx v1.10.3
- php v7.0.27
- File are served via CIFS/SMB from a QNAP NAS
Now, before moving to Nextcloud I was using ownCloud v8 directly on my QNAP. I decided to move to a raspberry pi because the QNAP is very limited. By the way, ownCloud v8 directly on the QNAP worked flawlessly.
I decided on moving to Nextcloud due to the 100% OSS nature of the project, but right from the begining I has issues with conflicts. I tried a little bit of everything. I fine tunned both MariaDB, nginx and PHP to make the best possible use of the hardware available on the raspberry pi, but issue was always present.
I finally decided to try ownCloud v10 on the raspberry, with basically the exact same set-up and configuration, and the issue is no longer present. I no longer have any conflicts when saving and using files.
It seems that I will therefore move back to ownCloud as Nextcloud is aparently unusable by me. What however I always found very strange is that no one else was complaining about this, so it led me to beleive it had to be something isolated to my instalation, but unfortuantely I was never able to understand what and it seems that ownCloud does not suffer from the same issue and so my decision is to move back.
I would test further but unfortunately due to the size of my shares, preparing, testing, indexing, syncing are tasks that take very long, in particular in a raspberry pi.