You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Frankly, I don't know if this is a problem with "server" or "desktop", but the overall effect/interaction is causing problems
Steps to reproduce
Install NC18.
In the web-interface navigate to a directory, click into the workspace area at the top. This causes NC server to create a Readme.md file (regardless of content).
Have a windows client syncing that folder.
Expected behaviour
A single readme.md file (in whatever case) is created, whether empty or with some content.
Actual behaviour
Three files with varying-case filenames are created.
Windows' based desktop clients repeatedly error. This results in a locked client, so files are not being synced.
Server configuration
Operating system: ubuntu 14.04 and 16.04
Web server: apache
Database: mysql (in one instance) and postgres-11.6 in another
PHP version: 7.2.16 on one and 7.3.13 in the other
Nextcloud version: NC-18.0.0 (from tarball) and NC-18.0.0-ce docker image
Updated from an older Nextcloud/ownCloud or fresh install: upgraded from 17.0.2 (both)
Where did you install Nextcloud from: tarball (first) and docker (second)
From that, I don't disagree that the server is not responsible for case-handling on the client, so that is certainly an issue for https://github.com/nextcloud/desktop. However, why are three files created? The fact that three files exist suggest the server had something to do with it, otherwise there would be only one.
I've cross-posted an issue as nextcloud/desktop#1755, which I think is more likely the cause. The logs there are more recent and detailed than here, albeit from only one of my two servers referenced here (it's the ubuntu 14.04 tarball-based installation). While I suspect that the client is certainly a problem here, I don't know if the server is complicit in anything. Keeping this open for the time being.
Mea culpa, the real culprit was that I was running nextcloud on a linux box but (this is what I forgot) the data directory was a Synology SMB export, which defaults to the windows way of filename case-insensitivity.
As suggested on a synology forum, the fix was to force Synology to edit /etc/samba/smb.conf and append case sensitive = yes in the [global] section.
Frankly, I don't know if this is a problem with "server" or "desktop", but the overall effect/interaction is causing problems
Steps to reproduce
Readme.md
file (regardless of content).Expected behaviour
A single
readme.md
file (in whatever case) is created, whether empty or with some content.Actual behaviour
Three files with varying-case filenames are created.
Windows' based desktop clients repeatedly error. This results in a locked client, so files are not being synced.
Server configuration
Operating system: ubuntu 14.04 and 16.04
Web server: apache
Database: mysql (in one instance) and postgres-11.6 in another
PHP version: 7.2.16 on one and 7.3.13 in the other
Nextcloud version: NC-18.0.0 (from tarball) and NC-18.0.0-ce docker image
Updated from an older Nextcloud/ownCloud or fresh install: upgraded from 17.0.2 (both)
Where did you install Nextcloud from: tarball (first) and docker (second)
Signing status:
Signing status
List of activated apps:
App list
The first system (ubuntu 14.04, tarball-based)
The second system (ubuntu 16.04, docker-based)
Nextcloud configuration:
Config report
First system (ubuntu 14.04, tarball-based)
Second system (ubuntu 16.04, docker-based)
Are you using external storage, if yes which one: no
Are you using encryption: no
Are you using an external user-backend, if yes which one: first no, second LDAP
LDAP configuration (delete this part if not used)
LDAP config
Second system (ubuntu 16.04, docker-based)
Client configuration
Browser: FF72
Operating system: win10_64
Logs
Web server error log
Web server error log
Nextcloud log (data/nextcloud.log)
Nothing related to my client or those files in the log.
The text was updated successfully, but these errors were encountered: