Description: For security and regulatory reasons my work's vpn restricts apps which are running locally on the desktop or laptop which is vpn'ed into the network. (While vpn'ed in we are using terminal servers or desktops we remote desktop to. Those machines are allowed to access the internet while vpn'ed in.) When I attempt to access a Libreoffice document on my local drive the app (such as Writer or Calc) starts but remains greyed out and unusable. Steps to Reproduce: 1. connect to a vpn which restricts internet access to applications which are running locally 2. open a Writer document or a Calc spreadsheet Actual Results: application starts but remains greyed out and unusable Expected Results: application starts and is usable Reproducible: Always User Profile Reset: No Additional Info: application starts and is usable
Thank you for reporting the bug. it seems you're using an old version of LibreOffice. 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.
Unfortunately I cannot update the LibreOffice version any further on that version of Ubuntu (14.04). I have to use that one in order to still have a Firefox version which supports the NAPI plugin for the VPN. Another way you can reproduce this is to access a network which requires an "usage acceptance" before it allows you to access the internet. Try opening a Libreoffice document and you will see the same result (greyed out and unresponsive). Clearly the app is trying to pull something from the internet and winding up unresponsive. Please identify what it is trying to pull and determine why the app hangs on it instead of moving on with its life cycle to a responsive state. In the meantime I will use my Ubuntu 16 or install an Ubuntu 18 and pull a more recent version of Libreoffice to prove the bug still exists.
You can use an appimage to conveniently test new versions: https://libreoffice.soluzioniopen.com/
(In reply to Buovjaga from comment #3) > You can use an appimage to conveniently test new versions: > https://libreoffice.soluzioniopen.com/ Please try with the appimage and give us feedback on this issue. Thanks in advance
Dear Dennis Wiatzka, 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 Dennis Wiatzka, 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