https://bugs.documentfoundation.org/show_bug.cgi?id=107443
--- Comment #9 from Mike Kaganski <mikekagan...@hotmail.com> ---
(In reply to Thomas Lendo from comment #8)
> For me, it's still a regression as it worked well until LibO 5.1.
Unfortunately I cannot see a reliable reproducing steps to be able to test.
As Aron has already explained, two things are considered when the dialogs are
chosen: if there is a lock OO-style file present; and if the document is locked
at filesystem level (i.e., out of the scope of LibreOffice). The logic is that
if the document is not FS-locked, but the lockfile is present, then we might
suspect that the lockfile might be stale from some crash, so it had only been
left by mistake; and in this case, we can suggest to ignore the lockfile. But
if the lockfile is accompanied by FS-lock, then we see that the file is indeed
used right now by some other application, and so we don't offer an option to
override the lockfile.
But I can imagine a situation when (esp. in multiuser environment) a document
had been checked to have no FS lock; but the lockfile is already present. Then
user decides to ignore the lock, so file is tried to open in RW mode. But in
the meantime, the document had been already locked by another application, so
the attempt failed, and RO mode resulted.
I even can imagine that happening because of concurrent MSO installation -
imagine this sequence:
1. User double-clicks a DOCX document on a network share, which has a stale
lockfile from a previous LO session.
2. LO checks the document file, sees no FS lock on it, but detects the
lockfile, and offers to override the lockfile.
3. In the meantime, a timeout elapses that prevents immediate file info display
in Explorer for files on network shares (the timeout prevents lags when working
with files on low-latency filesystems); the DOCX document that had been
selected in Explorer by double-click is started to be analysed by associated
shell extension (simply put, a MSO component opens it in the background to
extract author/stats/preview); and file gets locked for the time being (the
network latency might make this a lengthy operation).
4. User clicks "Open".
5. File cannot be open for editing - RO mode.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
