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).
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)
NEW per comment 1
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Can confirm the bug always happen with last LibreOffice release.
Using LibreOffice Version: 6.0.7.3 Build ID: 1:6.0.7-0ubuntu0.18.04.10 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); Calc: group on my Laptop. Try to save a text document on my nfs4 share on the server. As I can copy save and delete, the right are set valid. When saving, a file will be saved, but this is empty. It takes some time and then an errormessage pops up Error saving the document NAME: Error during shared access to PATH/NAME Thanks in advance
Confirmed on Debian 10, LibreOffice Version: 6.1.5.2 Build-ID: 1:6.1.5-3+deb10 NFSv3: Disabling File-Lock in the wrapper-script /usr/lib/libreoffice/program/soffice resolves the issue but (evidently) does not tackle the problem. NFSv4.2: problem does not occur NFS4 export options: rw,crossmnt,no_subtree_check,sync
This still happens with Libreoffice 6.3 on Ubuntu 19.10 and Ubuntu 18.04. Please consider converting this into an enhancement request to make debugging of this issue easier. The error messages in this case really should be improved to help figure out what the heck is going on i.e. check permissions where you are trying to save; Check NFS locking is working and how to do that; Try the file locally to see if issue goes away. This isn't an issue that an Unknown User has the file locked. It is an issue that Libreoffice was unable to do locking at all where the file was being written. This can quickly be found by copying the document you are trying to open to a local volume say /tmp and seeing if you can open it there. The "solution" where people turn off file locking is going to break a lot of things and should NOT be recommended. Switching to NFSv4 is overkill and not needed. I suspect differences in how locking is done on NFSv4 were why this helped some users. The solution here is straight forward but not obvious unless you can see the server logs. I could create my lock file manually for example .~lock.document.odt. I was not having permission problems. What I was having was NFS locking issues. I eventually found on my server when I looked at dmesg I had entries like: [67667.828919] lockd: cannot monitor ClientHostName The solution was on client and on server I had to enable rpc-statd as root: # systemctl enable rpc-statd; systemctl start rpc-statd That was enough to end the lockd errors and Libreoffice just worked as expected.
Dear Basic Six, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
On pc Debian x86-64 with master sources updated today, I did this: 1) create dirs "nfs_local" and "nfs_remote" in my home directory + create a file test.txt in "nfs_remote" 2) Install nfs server by following https://guide.ubuntu-fr.org/server/network-file-system.html Package: nfs-kernel-server Source: nfs-utils Version: 1:2.6.1-2 Installed-Size: 636 Maintainer: Debian kernel team <debian-kernel@lists.debian.org> Architecture: amd64 3) /etc/exports contains: /home/julien/nfs_remote localhost(rw,sync,no_subtree_check) 4) mount localhost:/home/julien/nfs_remote /home/julien/nfs_local 5) I opened "nfs_local" dir and opened "test.txt" to modify it, no pb. 6) I created a brand new file test.odt in "nfs_local", no pb too. Could someone give a new try with 7.3.4? (unless I missed something?)
Dear Basic Six, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Basic Six, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp
Many people who confirmed this earlier were not in the Cc of this report. I am now adding them. All: can you please test this again? This was closed automatically after Julien could not reproduce with the steps below and nobody reacted: (In reply to Julien Nabet from comment #9) > On pc Debian x86-64 with master sources updated today, I did this: > > 1) create dirs "nfs_local" and "nfs_remote" in my home directory + create a > file test.txt in "nfs_remote" > > 2) Install nfs server by following > https://guide.ubuntu-fr.org/server/network-file-system.html > Package: nfs-kernel-server > Source: nfs-utils > Version: 1:2.6.1-2 > Installed-Size: 636 > Maintainer: Debian kernel team <debian-kernel@lists.debian.org> > Architecture: amd64 > > 3) /etc/exports contains: > /home/julien/nfs_remote localhost(rw,sync,no_subtree_check) > > 4) mount localhost:/home/julien/nfs_remote /home/julien/nfs_local > > 5) I opened "nfs_local" dir and opened "test.txt" to modify it, no pb. > > 6) I created a brand new file test.odt in "nfs_local", no pb too. > > Could someone give a new try with 7.3.4? (unless I missed something?)