Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: in the case clash resolver, the name of the existing folder is missing #6011

Open
4 of 8 tasks
maximelehericy opened this issue Aug 30, 2023 · 2 comments
Open
4 of 8 tasks
Assignees
Labels
1. to develop approved bug approved by the team bug hotspot: filename handling Filenames - invalid, portable, blacklisting, etc.

Comments

@maximelehericy
Copy link

maximelehericy commented Aug 30, 2023

⚠️ Before submitting, please verify the following: ⚠️

Bug description

First folder created was "Test".
Second folder created was "test"
It triggers a case clash, and offer conflict resolution. However, in the conflict resolution window, the first folder name is missing.

...
image

Steps to reproduce

  1. create a folder TEST from the web interface
  2. sync your windows desktop client
  3. create a folder test from the web interface
  4. sync your windows desktop client
  5. CLick the Nextcloud icon in the taskbar, and select resolve conflict.
  6. The name of the first created folder "TEST" is not appearing.
    ...

Expected behavior

The name of the first created folder "TEST" should appear.
...

Which files are affected by this bug

test

Operating system

Windows

Which version of the operating system you are running.

Windows 11

Package

Appimage

Nextcloud Server version

27.0.1

Nextcloud Desktop Client version

3.9.3

Is this bug present after an update or on a fresh install?

Updated from a minor version (ex. 3.4.2 to 3.4.4)

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

Are you using an external user-backend?

  • Default internal user-backend
  • LDAP/ Active Directory
  • SSO - SAML
  • Other

Nextcloud Server logs

No response

Additional info

No response

@codeling
Copy link

codeling commented Sep 4, 2024

The exact same problem seems gone, but 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.

@andrepbento
Copy link

I have the same issue in macOS version 3.13.4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. to develop approved bug approved by the team bug hotspot: filename handling Filenames - invalid, portable, blacklisting, etc.
Projects
None yet
Development

No branches or pull requests

5 participants