Description: Hi, Our files a mounted via fstab (CIFS) on Ubuntu 16.04 LTS (kernel 4.15) and when we try to open a document (calc, writer, ...), libreoffice is totally blocked (before splash screen) for some seconds (~20-30 sec) and after that it open fine. It seems that this problem is not present with kernel 4.4.x and if i use vers=2.0 of CIFS it works with all kernels. It appears more often when the document is saved with a password. Don't know where is the problem (kernel or Libo) but if someone can test it. I do not have debug logs.. If someone can tell me how i can get some debug info, just tell me.. Thanks! Steps to Reproduce: 1. Mount a network folder over CIFS vers=3.0 in fstab. Use kernel 4.15 2. Open a libreoffice document (try with and without a password in document) 3. Try with a older kernel (4.4 by example) or also another Libreoffice version, 5.4, 5.3 Actual Results: LibreOffice block for ~20-30 seconds before open Expected Results: Have to open quickly without blocking Reproducible: Always User Profile Reset: No Additional Info: Not sure from which version of LibreOffice it begin. I enter 6.0.5 but i know is from older version. It happens on all our computers.
If you have enough disk space and patience, you could try bisecting the problem with our binary repos: https://wiki.documentfoundation.org/QA/Bibisect You need git installed. If you are certain the problem is not yet in 5.4, you would download this repository: git clone git://gerrit.libreoffice.org/bibisect-linux-64-6.0 Then to start things off you would do in the repo directory git checkout oldest instdir/program/soffice /path/to/remote/document Then confirm the problem is present in the latest: git checkout master instdir/program/soffice /path/to/remote/document If problem is not in oldest, but is in master, then start the process with git bisect start master oldest ...and follow the wiki instructions. Linux-specific stuff: https://wiki.documentfoundation.org/QA/Bibisect/Linux
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.
Dear MichaelB, 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 MichaelB, 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