https://bugs.documentfoundation.org/show_bug.cgi?id=101409
Bug ID: 101409
Summary: FILEOPEN lock status being incorrectly (and
dangerously) reported
Product: LibreOffice
Version: 5.1.5.2 release
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Calc
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: nigel.ar...@silson.com
Created attachment 126690
--> https://bugs.documentfoundation.org/attachment.cgi?id=126690&action=edit
Screenshot of the document-locked dialog
A document test.ods is present in an NFS v3 shared directory. User carmen on
client system apollo.silson.com opens the file for editing. The lock file is
created and contains the following text:
$ cat /silson/allshare2/SilsonR\&D/.~lock.test.ods#
,carmen,apollo.silson.com,09.08.2016
11:33,file:///home/carmen/.config/libreoffice/4;
(which also confirms that user nigel has read access to the lock file)
Now user nigel on atlas.silson.com attempts to open the (locked) file. The lock
is detected, but the dialog incorrectly reports the problem as follows (my
enphasis with **text**) (see attachment for a screenshot of the dialog)
=======
Document file 'test.ods' is locked for editing **by yourself** on a **different
system** since 09.08.2016 11:33
Open document read-only, or ignore own file locking and open the document for
editing.
Buttons:Open Read-only Button:Open Button:Cancel
=======
>From the contents of the lock file it is clear that LibreOffice ought to be
able to correctly report "... is locked for editing by **user carmen** **on
host apollo.silson.com ** ..." On our organisation this lets us find or phone
the user who has the file open and ask them whether they can close it.
Further, in this situation the option to ignore the lock and open the file (not
read-only) is extremely dangerous, leading to data loss if/when a naive user
takes this choice.
This is a regression. It worked correctly using Libreoffice 4 (not sure which
version: the one which came with Fedora 20 which is now eol.
A similar problem occurs when the file is opened via Samba/CIFS from an
instance of LibreOffice running on a Windows PC.
The same bug is present in Libreoffice 5.2.0.4 release
Further information on file ownership / protection, if relevant. Both nigel and
carmen are members of group silson. Collaboration takes place using shared
group write access. There are no acls affecting nigel or carmen.
[atlas: ~]$ ls -l /silson/allshare2/SilsonR\&D/.~lock.test.ods#
-rw-rw-r--+ 1 carmen silson 85 Aug 9 11:33
'/silson/allshare2/SilsonR&D/.~lock.test.ods#'
[atlas: ~]$ ls -l /silson/allshare2/SilsonR\&D/test.ods
-rwxrwxr--+ 1 nigel silson 22899 Aug 8 13:30
'/silson/allshare2/SilsonR&D/test.ods'
--
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
