https://bugs.documentfoundation.org/show_bug.cgi?id=160315
--- Comment #8 from Peter <[email protected]> --- I can confirm this issue on Windows 10 after upgrading to LibreOffice 26.2.0.3 (x86_64). Environment: LibreOffice 26.2.0.3 (x86_64) Windows 10 22H2 (19045) SMB3 network share (Synology NAS, Btrfs) Wired connection SMB min SMB2 / max SMB3 Oplocks disabled Durable handles disabled Recycle bin disabled No advanced share ACLs Behaviour: Open .docx or .odt file from SMB share. Close LibreOffice. .~lock.filename# file remains in the directory. Attempt to save over the same file. Error appears: “Could not create a backup copy.” Important observations: The lock file can be manually deleted. The original file can be renamed or deleted manually. New files can be created in the same folder. No soffice processes remain running after closing LibreOffice. The issue reproduces on multiple Windows machines. A brand new shared folder reproduces the same behaviour. Saving locally (e.g. C:\Temp) does not leave lock files and works normally. Regression: This behaviour started immediately after updating LibreOffice. Previous version did not exhibit this problem. This appears to be a regression in network lock cleanup / safe-save handling over SMB shares. -- You are receiving this mail because: You are the assignee for the bug.
