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

Client aborts sync in case of upload fails to an read-only shared folder #7371

Open
5 of 8 tasks
Elleven1 opened this issue Oct 20, 2024 · 2 comments
Open
5 of 8 tasks

Comments

@Elleven1
Copy link

⚠️ This issue respects the following points: ⚠️

Bug description

Using Windows sync client V3.14.1 synchonization ends without any error message, but no files are synchronized. Searching in the local log files it leads to the root cause. A shared folder with a missing right for the user to create new files, where the user stored a file locally. Than during sync scan the scanning process ended without uploading or downloading files to/from any other folders. After enabling the right for creating new files to that dedicated shared folder, the sync process completed successfully as expected.

The point is, that the process ends completely in such a case without synchronizing anything. My expectation would be, that just that single file cannot by synchronized due to the missing rights and that the user would get an error massege in the client window.

Virtual files are enabled

Steps to reproduce

  1. Share a folder to any user
  2. In the user defined rights (Benutzerdefinierte Berechtigungen in German) enable all rights except create (Erstellen in German)
  3. Setting up the windows client for that user with enabled virtual files
  4. Wait, until initial synchronization has completed
  5. Creaty any file in that shared folder locally on the user's machine
  6. Nothing get's synchonized anymore

Expected behavior

  • All syncronizations should proceed as usual except that dedicated file, which was created locally
  • The user getts an error message in the windows client

Nextcloud Server version

30

Operating system

Debian/Ubuntu

PHP engine version

PHP 8.3

Web server

Apache (supported)

Database engine version

MariaDB

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

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other

Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

@joshtrichards joshtrichards transferred this issue from nextcloud/server Oct 20, 2024
@joshtrichards joshtrichards changed the title [Bug]: Windows Client aborts sync in case of upload fails to an read-only shared folder Client aborts sync in case of upload fails to an read-only shared folder Oct 20, 2024
@FriedVariable
Copy link

Same here for macOS. Need a quick fix please.

@Elleven1
Copy link
Author

I've tested this issue with 3.13.4 and 3.14.0. Issue is the same there

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