Bug Hunting Session
Bug 107911 - All apps hang on startup with NFS4 home directory if .lock exists and is incorrect
Summary: All apps hang on startup with NFS4 home directory if .lock exists and is inco...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.3.2.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Network
  Show dependency treegraph
 
Reported: 2017-05-17 14:01 UTC by mal
Modified: 2019-06-08 02:56 UTC (History)
2 users (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 mal 2017-05-17 14:01:24 UTC
If you use LO on Linux ( openSUSE in my case ) with NFS4 home directories all LO apps can hang on startup. Applies to both openSUSE version and generical LO version. 

To reproduce without NFS4 :-

Start Writer

Open the .lock file with a text editor

Close Writer ( The lock file gets removed )

Re save the .lock file after changing the hostname  ( ie as if a user has crashed or just turned off their machine and then gone to another machine )

Start Writer ( it hangs on startup )

It now cannot be restarted until all LO processes have been killed or user logs out and back in if just the faulty .lock is removed or user logs into the machine where it died ( or changes the .lock to the current machine )

Removing the whole ~/.config/libreoffice will also clear it as LO seems to understand that.

Quick and dirty fix:-

add 
rm ~/.config/libreoffice/4-suse/.lock to .profile
or
rm ~/.config/libreoffice/4/.lock to .profile
depending on your version
Comment 1 Xisco Faulí 2018-10-19 11:08:59 UTC
Thank you for reporting the bug.
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 2 QA Administrators 2019-05-08 17:30:25 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2019-06-08 02:56:10 UTC
Dear mal,

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