Created attachment 121523 [details] configure options used and the output from "soffice --valgrind" command Compiled 64-bit version of Libreoffice (any recent version, including 5.1.0.1), using attached configuration flags. The compilation went fine. However. when running "soffice" command (with or without any flags), the splash logo appears with a pixel-wide progress bar and that's where it freezes and just sits there, without any errors or anything. Attached is the configuration flags used, and the output from "soffice --valgrind" command
which is the earlier release you saw this issue?
I have not seen this issue while I was compiling Libreoffice (any version) on purely 32-bit Linux machine. I have started seeing this issue on a new 64-bit Linux machine (i7-IvyBridge chip) I built to replace old 32-bit machine. I see this issue on any libreoffice version 5.+. The older version won't even compile.
What if you launch it with SAL_USE_VCLPLUGIN=gen soffice
Looks like you're running with Gtk3 backend. And you have a lot of disabled features. Maybe you found a non-working combination with OpenGL. So please try running with the gen backend and disable opengl: export SAL_DISABLEGL=1 export SAL_USE_VCLPLUGIN=gen And you won't need to build with all those "--without-system-*" options, as the default always downloads and builds the required libraries just for LO. Did you ever had a version building and running with all those options on 32bit? I suggest getting rid of most of them and don't use experimental features like "--enable-mergelibs". You can re-add additional options later.
I tried running soffice with export SAL_DISABLEGL=1 export SAL_USE_VCLPLUGIN=gen and it did not change anything. It still freezes on startup. I noticed it also creates [soffice.bin] defunct process. Apparently waitpid() call is missing somewhere in the code. I'm going to upload complete build configuration and build log and screen print
Created attachment 121621 [details] Build configuration, config_host.mk file, make log This is complete build information with make log
Created attachment 121622 [details] screen print
please tell if the issue is still present in recent 5.1.x releases. 5.1.2.2 official release and 5.1.3.2 release candidate are available
Dear Bug Submitter, 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-20170502
Dear Bug Submitter, 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-20170531