[BUG] Linux client fails to sync read-write shares subfolders of read-only shared folder

[A-Aurel]

⚠️ 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

User U1 has a folder structure as MAIN/SUB-RO and MAIN/SUB-RW

User U1 shares with user U2:

• MAIN as read-only
• SUB-RW as read-write

U2 sees and syncs at his root both MAIN and SUB-RW

U2 can NOT make modifications in SUB-RW.
The client returns a failure in the sync activity shown for MAIN/SUB-RW

Steps to reproduce

User U2 makes any modification in SUB-RW

The client returns a failure in the sync activity shown for MAIN/SUB-RW

Expected behavior

U2 can make any modification in SUB-RW

Which files are affected by this bug

Any

Operating system

Linux

Which version of the operating system you are running.

Fedora 40

Package

Distro package manager

Nextcloud Server version

29.0.2

Nextcloud Desktop Client version

3.13.0

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

Fresh desktop client install

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

Cannot find any error nor warning

Additional info

All works when doing things from the web interface.
So it seems that is only the latest Linux Nextcloud-client update, which attempts to upload a change to the read-only master folder, rather than to the current shared subfolder (with modifications rights).

[A-Aurel]

All works good using AppImage 3.12.5 as well as Fedora 40 rpm version 3.12.5.
It seems the linux permission as r-- for MAIN/SUB-RW folder is creating the problem.

[A-Aurel]

#6839
The AppImage fixed the problem ! Thanks