Bug Hunting Session
Bug 93117 - LibreOffice freezes when trying to access/open/read/write documents on NFS mounts
Summary: LibreOffice freezes when trying to access/open/read/write documents on NFS mo...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.3.3.2 release
Hardware: Other Linux (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Network
  Show dependency treegraph
 
Reported: 2015-08-04 11:32 UTC by Basic Six
Modified: 2019-09-19 08:34 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Basic Six 2015-08-04 11:32:31 UTC
LibreOffice is unable to access files on NFS mounts (at least NFSv3).
When trying to open a remote (odt) file, the splash screen freezes. The process has to be killed (SIGKILL). Opening a file in read-only mode appears to work.
Same thing when trying to save a file on an NFS mount. The window freezes, it's not even possible to select and copy the text to the clipboard, it's gone. I lost a document because I forgot to copy everything to the clipboard before saving - in case LibreOffice crashes.
Interestingly, the file was created (but it's empty), along with a LibreOffice lock file (".~lock...").

This basically makes LibreOffice impossible to work with, on a central NFS storage, at least by default. Given that a central storage for all data is a very common setup, this is a significant bug. When trying to save, this can even cause data loss. The safe workaround is copying the file to the local system, edit it locally and then move it back to the storage.

Using the default LibreOffice from the Arch repository:
LibreOffice 4.3.3.2 430m0(Build:2)
NFSv3 is used (hard - nolock option is *not* used)

It's frustrating that some people seem to suggest using the nolock mount option, or even worse, migrating everything to NFSv4. Besides certain issues like NFSv4 sometimes having issues when NFSv3 works perfectly fine, it's not a proper solution to migrate NFS because of LibreOffice.
The Arch documentation recommends modifying the LibreOffice wrapper script /usr/lib/libreoffice/program/soffice:
https://wiki.archlinux.org/index.php/LibreOffice#Hanging_when_using_NFSv3_shares
However, none of this is limited to one distribution (like Arch) and no regular person will/should edit a shell script in order to make LibreOffice work. (And what happens when updating, the script might be replaced.)
Again, telling an end user to hack in shell scripts has nothing to do with a solution. If the locking feature isn't working by default, maybe it should be disabled by default?

I have found similar bugs regarding this issue, but no actual solution so far. For example, there is an old OpenOffice bug which was closed (without solution) because "Go_oo does not exist anymore". There are similar LibreOffice bugs, but there are differences, some describe a problem when opening only but not when saving, others describe error messages (there's no error message here).
Comment 1 j.rios 2016-05-17 16:43:18 UTC
I do confirm having theses exact same glitches under archlinux and my server mount using NFSv3, hangs even loading an existing file from the nfs mountpoint.

Thanks for the solution Basic Six x)
Comment 2 Buovjaga 2016-05-25 19:18:10 UTC
NEW per comment 1
Comment 3 QA Administrators 2018-05-30 02:38:43 UTC Comment hidden (obsolete)
Comment 4 Cédric Bellegarde 2019-09-19 08:34:39 UTC
Can confirm the bug always happen with last LibreOffice release.