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]: New folder with 3.13.2 #6900

Open
5 of 8 tasks
Mika-6-9 opened this issue Jul 10, 2024 · 1 comment
Open
5 of 8 tasks

[Bug]: New folder with 3.13.2 #6900

Mika-6-9 opened this issue Jul 10, 2024 · 1 comment
Assignees

Comments

@Mika-6-9
Copy link

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

Bug description

Error message when creating a new folder

Steps to reproduce

  1. Create a new folder
  2. Rename the folder before confirming
  3. Sometimes an error message appears saying that it cannot synchronize the “new folder” folder which does not exist

Expected behavior

Not showing an error / Trying to sync a folder that doesn't exist

Which files are affected by this bug

Explorer

Operating system

Windows

Which version of the operating system you are running.

Windows 10 et 11

Package

Official SNAP package

Nextcloud Server version

27

Nextcloud Desktop Client version

3.13.2

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

2024-07-10 10:46:22:759 [ warning nextcloud.sync.propagator C:\Users\User\AppData\Local\Temp\windows-24285\client-building\desktop\src\libsync\owncloudpropagator.cpp:288 ]:	Could not complete propagation of "PROJETS/nomprojet/Fournisseurs/Nouveau dossier" by OCC::PropagateRemoteMkdir(0x1a457912900) with status OCC::SyncFileItem::FatalError and error: "Erreur inconnue"

Additional info

Looks like an error already resolved in a previous version:
#5824 and #5420 and #6500

@camilasan
Copy link
Member

Thanks for the feedback, I will investigate this.

@camilasan camilasan self-assigned this Jul 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants