Bug 96215 - LibreOffice hangs/won't start if some mounted shares are inaccessible
Summary: LibreOffice hangs/won't start if some mounted shares are inaccessible
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Network
  Show dependency treegraph
Reported: 2015-12-02 22:41 UTC by Saren Tasciyan
Modified: 2021-11-13 07:57 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:
Regression By:


Note You need to log in before you can comment on or make changes to this bug.
Description Saren Tasciyan 2015-12-02 22:41:49 UTC
I had issues with LibreOffice and it's freezing hanging problems for a while. Now I figured it out, what actually the problem is. Here is the scenario:

I am running Ubuntu 14.04 LTS on my laptop for work with automatically mounted network shares (with kerberos tickets). Everything works fine when I am at work (connected to network at work). But when I start my laptop (wake up) at home, opened LibreOffice windows hang (turn grey and unresponsive) and simply never recovers! Also restarting doesn't help. I can't even see the splash screen! It simply runs with 0 CPU usage in the background. I kill it and try again but no use. There was a similar problem with Inkscape. So I connected to my work network from home with VPN, which made those shares accessible. I checked if they are accessible through nautilus. Then LibreOffice starts and works normally.

There are no program related files in those shares. LibreOffice does not require anything there to start. There are probably some documents there, which I accessed before. But I am not trying to open them.

Expected behaviour would be that LibreOffice handles those IO operations either asynchronously or simply not at all. Also in case of such emergencies a time out needs to be present. Network shares are not accessible all the time but these are mounted as folders in the root directory. I wonder if any application can detect if they are not locally stored or not (unless they look into that in detail).

So please don't hesitate to ask for more relevant information. I will provide as much as I can.

Comment 1 Liam Ward 2015-12-18 15:28:45 UTC
+1 for this. I have exactly the same problem and it usually requires a reboot to resolve it.
Comment 2 Buovjaga 2015-12-22 15:24:10 UTC

Liam: are you also using Kerberos?

Or maybe this has the same root cause as bug 41987?
Comment 3 Buovjaga 2016-04-18 05:38:20 UTC
Saren set this to NEW, but it would be great to get more details from Liam.
Comment 4 Florian 2016-06-23 11:51:05 UTC
I have quite similiar behavior, I hope my description helps:

User Action:

Action 1: This Action is only mentioned to show that normally everything works fine: Laptop Connected to LAN, Starting up a VPN connection, mounting cifs Share by shellscript. Opening a LOCAL LO file (e.g. LibreOffice Calc Spreadsheet). Everything works fine. Closing LO.

Action 2: No the Action is resulting in unwanted result:
Closing down the VPN connection, NOT unmounting the shares. 
Starting LO without any document:

Result: LO hangs. 

Expected Resulted: LO works normally, (of course would be allowed to run in a timeout when trying to access the mounted but not connected shares).

Unmounting the shares -> LO start up normally. 
Sometimes it also helps to clear the "Recent Files".

My Guess:
LO tries to access the files of "Recent Files" - and this hangs when the share is not valid any more.

Version:,  Build ID: 1:5.1.3-0ubuntu1
Ubuntu 16.04 LTS   64bit  english
Comment 5 Florian 2016-06-23 11:52:46 UTC
sorry, in description of Action two the correct line would be:

Action 2: _Now_ the Action is resulting in unwanted result:
Comment 6 Saren Tasciyan 2016-06-23 12:01:29 UTC
Regarding the unmounting shares: I am currently using this as a work around. I unmount the shares, then LO works fine. Sometimes, I forget to unmount, then LO hangs again. For that, I need to connect VPN again, let all the IO finish then unmount.
Comment 7 Saren Tasciyan 2016-11-09 13:36:58 UTC
The issue persists in Ubuntu 16.04 LO
Comment 8 QA Administrators 2017-12-18 03:26:33 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2019-12-19 03:31:19 UTC Comment hidden (obsolete)
Comment 10 Fiable.biz 2021-11-13 06:42:15 UTC
This bug was fixed and reappeared in version 7.2, it seems. See bug #144566. So I mark this one as fixed.