Steps to reproduce: 1. Download attachment 109322 [details] from bug 86188 2. Convert it to odt with: instdir/program/soffice --convert-to odt <path_to_file>/test2_converted.docx --outdir <output_path> -> LibreOffice prompts the error: "Error: source file could not be loaded" In the past, even if the document was corrupted, convert-to worked and the fail was converted Reproduced in Version: 7.0.0.0.alpha1+ Build ID: 82894d85147840f1f587e9530b12f0058f2ef2c3 CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded [Bug found by office-interoperability-tools]
Hi Mike, This issue started to happen after https://cgit.freedesktop.org/libreoffice/core/commit/?id=9fdf8c0a5cc036ea9bd1e11dd8f2c1a6e601fae2. The commit message talks about "this will start showing parse errors on invalid files which previously just opened without warnings" This is no the case for the file mentioned in this ticket, LibreOffice already shows a warning even before the commit, as is doing after the commit, the problem is only happening when using --convert-to from commandline. I'm not sure whether it's a bug or it's the expected behaviour that's why I've reported it so you can decide Thanks in advance
It's interesting why did it pass previously (when correctly warning in UI). Now it behaves consistently with other corrupt documents. E.g., see bug 128820, where the DOCX from attachment 155841 [details] was already not converted before the said patch. --convert-to must not silently process corrupted documents - at least I think so. My point of view on if we should allow that in --convert-to might be wrong; and if so, a separate bug needed to allow processing invalid files (as if user accepted), or add some additional switch to do that... (personally I still consider that wrong, because that would make processing unstable).
(In reply to Mike Kaganski from comment #2) > It's interesting why did it pass previously (when correctly warning in UI). > Now it behaves consistently with other corrupt documents. E.g., see bug > 128820, where the DOCX from attachment 155841 [details] was already not > converted before the said patch. --convert-to must not silently process > corrupted documents - at least I think so. Yep, it makes sense to be consistent and fail for all corrupted files. Let's close it as RESOLVED NOTABUG Thanks for your help