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

• This is a bug, not a question or a configuration issue.
• This issue is not already reported on Github (I've searched it).
• Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
• I agree to follow Nextcloud's Code of Conduct

Bug description

When someone with read-write permission of a folder create a new file inside it and I try to synchronise again the folder whereas I only have read permission, there is an error in the synchronisation "Permission denied".

Steps to reproduce

1. User 1 creates a folder with read-write permissions for them and read-only permission for user 2.
2. User 2 synchronises the folder.
3. User 1 creates a file inside the folder.
4. User 2 tries to synchronise the folder again a gets an error permission denied.

Expected behavior

The file is created inside the folder. The permissions are set correctly for the folder (read-only) and for the file (read-only too).

Which files are affected by this bug

All files created inside a read-only permission folder

Operating system

Linux

Which version of the operating system you are running.

Fedora Linux 39

Package

Appimage

Nextcloud Server version

29.0.2.2

Nextcloud Desktop Client version

3.13.1

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

I did not noticed this bug in #6796 which was happening when a read-only permission file was modified but is related to the way permission are managed by Nextcloud Desktop for Linux. The branch #6839 did not fix the problem (as it happens with version 3.13.1).