I see several questions about unlocking files but none seems to match my circumstances.
My files reside on a CentOS 6 server. I am trying to edit them using Windows 7 and a product called ExpanDrive (v2.4.0). ExpanDrive exposes my server’s files (using sftp) as a virtual drive in Windows. This set-up has been stable for a couple years on several different computers and as far as I know, nothing has changed about the CentOS server or ExpanDrive but I am experiencing this problem on a new computer and a new installation of ExpanDrive and a fresh install of LO (22.214.171.124).
Suddenly, today, whenever I open a .ODT file using Writer/LO, I get a message like this:
“Document file ‘xxxxxxxxxx.odt’ is locked for editing by:
Open document read-only or open a copy of the document for editing”
There are no visible lock files (i.e., not visible in Windows 7 and not visible in an ls -a on the server.) When I try to open a .DOC file in the same directory, everything works and I can see that the lock file is created (and then removed correctly when I close the file).
This seems to affect files in all directories (i.e., 100% of the several folders which I tried) and affects .ODS files as well as .ODT files.
Can network latency cause this kind of problem? This kind of drive always has some latency and today it’s like molasses…