[Libreoffice-bugs] [Bug 122192] New: Converting docx in headless mode hangs
bugzilla-daemon at bugs.documentfoundation.org
bugzilla-daemon at bugs.documentfoundation.org
Wed Dec 19 10:24:18 UTC 2018
https://bugs.documentfoundation.org/show_bug.cgi?id=122192
Bug ID: 122192
Summary: Converting docx in headless mode hangs
Product: LibreOffice
Version: 5.3 all versions
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: LibreOffice
Assignee: libreoffice-bugs at lists.freedesktop.org
Reporter: rb at awave.com
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/
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20181219/b185909a/attachment-0001.html>
More information about the Libreoffice-bugs
mailing list