Following on from petermau’s answer, there is lock information kept within the ODT file as well as outside that file in the local lockfile + in the profile lockfile.
I’m currently editing a document under Debian 6.0 which I previously worked on under winXP. XP crashed whilst I was working on it & it was next visited under Debian. Attempting to open that file gave the following dialog message:
Document file ‘html5.odt’ is locked for editing by:
Alex Kemp ( 25.05.2015 13:34 )
It then offered:
Open document read-only or open a copy of the document for editing.
I chose the second option & have been adding to it ever since. The one strangeness is that I can no longer revert the new file’s name back to the old, as LO then thinks that I am attempting to open the old locked document.
The info given by the 2 Peters is perfectly accurate in my experience, and I thought to add some extra in the hope that it may be interesting.
Lock info:
Windows XP:
local lockfile: .~lock.html5.odt#
local lockfile contents:
{username}, {computer-name}/{user-short-name}, {computer-name}{time-stamp}{profile-lockfile-location}
actual local lockfile contents (example, different file):
Alex Kemp,DAVID/Alex,david,25.05.2015 13:34,file:///C:/Documents%20and%20Settings/Alex/Application%20Data/OpenOffice/4;
Profile lockfilename: .lock
Profile lockfilename contents:
[Lockdata]
User=DAVID/Alex
Host=DAVID
Stamp=38D0D54DAFCA1BD797B08396CA60D632
Time=Mon May 25 12:00:53 2015
IPCServer=true
Debian 6.0:
local lockfile: .~lock.html5.0.odt#
local lockfile contents: (identical format to XP)
Profile lockfilename location: /home/alexK/.config/libreoffice/4/.lock
Profile lockfilename contents: (identical format to XP)
Final comment: the XP lockfiles detailed above were not mounted when I attempted to load the XP-originated file. Thus, the information within the dialog could only have come from the .odt file, not the lockfiles. Spookily, I obtained the dialog text above by re-attempting to load the locked XP-file. It’s lockfile is open in my debian directory right now & has the identical content to the “actual local lockfile” quoted above, including Windows folder.