Description: My application runs on a Ubuntu 16.04 web server where uploaded files automatically get's converted to PDF with doc2pdf which is part of unoconv which again uses Libreoffice in headless mode. When trying to convert the corrupted DOCX document hangs with 100% of the CPU utilized and eventually I have to reboot to recover. Steps to Reproduce: 1. Have a Word document (DOCX) that is corrupted 2. Try to convert it to PDF: libreoffice --headless --convert-to pdf broken.docx 3. Trying with a Word document that is not corrupted works fine Actual Results: When trying to convert the corrupted DOCX document hangs with 100% of the CPU utilized and eventually I have to reboot to recover: javaldx: Could not find a Java Runtime Environment! Warning: failed to read path from javaldx W: Unknown node under /registry/extlang: deprecated W: Unknown node under /registry/grandfathered: comments W: Unknown node under /registry/grandfathered: comments Fontconfig warning: ignoring UTF-8: not a valid region tag convert /home/forge/broken.docx -> /home/forge/broken.pdf using filter : writer_pdf_Export Expected Results: Command exits to shell with an error. Reproducible: Always User Profile Reset: No Additional Info: I would suggest one of these things would happen: 1. Command exits with an error 2. Set a timeout and if reached, the command 3. Be able to detect if DOCX document is broken Unfortunately I cannot provide you with the broken Word document because it contains sensitive information. Trying to censor the sensitive information would require me to create an new document that is not corrupted. Originally the question was asked here (and will attach a text version to this bug report): https://ask.libreoffice.org/en/question/174451/converting-docx-in-headless-mode-hangs/
Created attachment 147666 [details] Report posted on Libreoffice forums
please attach your corrupted DOCX file. You can erase all sensitive information by replace all symbols to letter "a"
Created attachment 148213 [details] Broken DOCX document Since DOCX is "just" a zip file a managed to unzip it, remove the sensitive data and the zip it again while keeping the broken state.
Doesn't hang for me with headless conversion of attachment 148213 [details] Can you try with 6.2.x or with 6.3, which is in release candidate state? Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away. Arch Linux 64-bit Version: 6.4.0.0.alpha0+ Build ID: 1ce1c26dd98e6477139e08d1ebe89fa950ff5fb0 CPU threads: 8; OS: Linux 5.2; UI render: default; VCL: gtk3; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded Built on 12 July 2019
Dear rb, 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 rb, 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