https://bugs.documentfoundation.org/show_bug.cgi?id=174200

--- Comment #1 from cs-hv <[email protected]> ---
To describe our setup more in detail:

We are running a Linux server hat offers an SMB share.
This share is mounted to the windows drive W:
Working on this share with LibreOffice documents is as expected.

For critical data we have an encrypted drive (end-to-end encryption).
On the device W: a folder W:\confidential has been created.
Using cppryptfs.exe 1.4.4.10 (wich is based on Dokan_x64 2.3.1.1000) an
encrypted file system is created in this folder which is mapped to another
windows driver letter.

The stale .~lock-files after editing documents appeared since version 26.8.0 of
LibrOffice (and today tested with version 26.8.3.1).

The stale .~lock-files do not appear on drive W: (i.e. the basic SMB share) and
do not appear when the encrypted drive is mapped to a local disk.
It seems to be the "stacked" combination of encryption and SMB.

I know that this combination is a bit "special" but has been working for long
time without any hassle although a bit slow.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to