[Bug]: (VFS) - Read-only attribute of a previously Locked file is not synchronized in the first time the file is opened on the desktop client

[vagner-dias]

⚠️ 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 a shared file is already locked by a user in Nextcloud and another user wants to open the same file for the first time, nextcloud synchronizes the locked file without the read-only attribute and allows the second user to edit the already-locked file

Steps to reproduce

Scenario:

• 2 Users: UserA and UserB have access to FileA
• Both users are using nextcloud desktop sync app.
• Temporary files lock application is enabled on the server

UserA has FileA already synchronized on its computer
UserB does not have FileA synchronized

UserA locks FileA and starts to editing it

UserB opens FileA for editing

At this moment, FileA is synchronized for UserB, however, the Read-only attribute is not set on the file, allowing UserB to edit the file.

Expected behavior

FileA should be synchronized for UserB with the Read-only attribute set, so that the file would not be edited by both users

Which files are affected by this bug

Any file accessible by more than one user

Operating system

Windows

Which version of the operating system you are running.

Windows 10

Package

Distro package manager

Nextcloud Server version

24.0.5

Nextcloud Desktop Client version

3.6.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

No response

[Mika-6-9]

Hello.
I think it's closed with #5841