Attention possible case sensitive clash - no conflict resolution provided

[ferdiga]

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Expected behaviour

clicking on the error message should open a meaningful message.
"meaningful" - as I do not understand the source of the error I can't say what is meaningful

Actual behaviour

the error message points to a directory - I do not see any case sensitive issues in the directory name.

Steps to reproduce

1. automatic sync

Client configuration

Client version: Version 3.2.0 (macOS).

Operating system:
macOS 11.3.1
OS language:

Qt version used by client package (Linux only, see also Settings dialog):

Client package (From Nextcloud or distro) (Linux only):

Installation path of client:

Server configuration

Nextcloud version:
20.0.9 on a Hetzner storage service
Storage backend (external storage):

Logs

Please use Gist (https://gist.github.com/) or a similar code paster for longer
logs.

1. Client logfile:
   Since 3.1: Under the "General" settings, you can click on "Create Debug Archive ..." to pick the location of where the desktop client will export the logs and the database to a zip file.
   On previous releases: Via the command line: nextcloud --logdebug --logwindow or nextcloud --logdebug --logfile log.txt
   (See also https://docs.nextcloud.com/desktop/3.0/troubleshooting.html#log-files)

2. Web server error log:

3. Server logfile: nextcloud log (data/nextcloud.log):

[FlexW]

Could you provide us a screenshot from the error message or tell us what the error message said? Can you provide us any steps we can take to reproduce the exact same error message?

[ferdiga]

Meanwhile I upgraded the desktop client to 3.2.1

[ferdiga]

I migrated from a ubuntu 20.04 to a Macbook

• copied all files with rsync -av from the linux machine to the Macbook
• installed nextcloud client and choose the copied directory as root for the sync - choosing to keep existing files
  this works fine except a few files producing an error

BTW I had this error already on linux machines doing the same

[allexzander]

Hard to say how this can be improved. Maybe, pointing out the exact file name that is attempted to be copied and the file name of an already existing file that results in a clash. This will surely increase the length of the error message that doesn't fit nicely in the limited space of the UI it is displayed in.

Shouldn't the filename in the error message make a user gonna want to check that file on the server? It's a nice hint already.

Not sure myself. I've faced this issue when having two similarly named files having capital and the normal case of extensions (one is .PNG, while another is .png). While this works on Linux, this doesn't work on Windows. Looks like this doesn't work on mac OS too.

[ferdiga]

Well, I mentioned - I copied the files from Linux to Mac using rsync - hence the filename should be literally the same. (except rsync changes file names)
The linux machine was synced to the NC using th NC desktop on Linux and synced again using NC desktop on MAC

The design of the error messages should be made more readable any way.
see also
#3276

[ferdiga]

Hi,
definitely an upper/lower case issue.
after renaming the file - sync works, it's just a painful experience to rename some 100 files

[ferdiga]

I fixed the problem manually,
what can I provide?

[FlexW]

@ferdiga Everything is fine. I guess we will improve the error message.

[gege2b]

Hi
I just had the same problem between linux and windows clients
I renamed a bunch of files from MiXEdCase filename to lowercase filename on my linux box, the filenames basically didn't change except the case

And right now, my windows client show me a conflict error for each renamed files, and is uploading back the MiXedCase files, creating hundreds of duplicates on my linux client.

both clients are 3.4.4 (on windows 10 and mint 20)
Server is 23.0.4

[marbx]

Similar to #4103

[maximelehericy]

So now a conflict resolution is provided see picture below.

however, the existing filename is empty, so it requires the user to search for the existing filename prior setting the new name.

[codeling]

case clash conflict resolution still has an issue for me (client 3.13.3). the dialog shows a filename but clicking OK just leads to the dialog staying open and the OK button being grayed out.