[Bug]: File Locking - When a User Opens a Office file loses the connection the file gets locked indefinitely

[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

If a User Opens a Office file loses the connection the file gets locked indefinitely

Steps to reproduce

User A opened an Office file, effectively locking it. However, the same user abruptly shut down the computer. Several hours later, the file remains locked.

Expected behavior

A mechanism should be in place to detect when the user is no longer online and automatically unlock the file.

Which files are affected by this bug

Any office file

Operating system

Windows

Which version of the operating system you are running.

Windows 10

Package

Appimage

Nextcloud Server version

26.0.5

Nextcloud Desktop Client version

3.10.0

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

[vagner-dias]

@mgallien - I've recently come across this scenario involving file locking.

Regards

[jospoortvliet]

This is what the time-out for file locks is for, it's not something the desktop client can fix. A 30 min or 60 min time-out is wise.

https://github.com/nextcloud/files_lock#settings for how to set it.

It might make sense to set this as default, but either way - as the desktop isn't running, it can't fix this.

[robertofabrizi]

This is what the time-out for file locks is for, it's not something the desktop client can fix. A 30 min or 60 min time-out is wise.

https://github.com/nextcloud/files_lock#settings for how to set it.

It might make sense to set this as default, but either way - as the desktop isn't running, it can't fix this.

Is there a way to set this via docker-compose?
More importantly, after having set a new timeout (which is being applied to new locks as seen in oc_files_lock) how do I "unlock" files in groupfolders? Deleting the oc_files_lock and firing a occ groupfolders:scan 20 didn't remove the pre-existing locks.
Thank you!