Bug 150399 - SAXException: GUI permits "ignore error", CLI has no feature.
Summary: SAXException: GUI permits "ignore error", CLI has no feature.
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.3.0 release
Hardware: x86 (IA32) Linux (All)
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Commandline
  Show dependency treegraph
 
Reported: 2022-08-13 14:11 UTC by Arif Driessen
Modified: 2022-08-14 07:46 UTC (History)
0 users

See Also:
Crash report or crash signature:
Regression By:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arif Driessen 2022-08-13 14:11:20 UTC
Description:
Opening a .docx that may contain corrupt or invalid XML data in headless mode will fail to open, However, the GUI offers a dialogue that allows the user to ignore any errors and open anyway.

I would like a commandline switch, such as `--ignore-errors` that allows the CLI to do a best effort, just as the GUI does, rather than failing with "Error: Source file could not be loaded"

Steps to Reproduce:
1. run a corrupt .docx such as one found here: https://ask.libreoffice.org/t/help-saxexception-word-document-xml-line-2-attribute-w-cstheme-redefined/60704

with the command: `soffice --headless --invisible --nodefault --nofirststartwizard --nolockcheck --nologo --norestore --convert-to pdf <PATH_TO_FILE>`

Observe the error: `Error source file could not be loaded`

2. Open an instance of LibreOffice GUI, then run the command again.

When prompted, press "Yes" to ignore errors.

3. Command will exit successfully, and a pdf file has been created.

Actual Results:
No ability to successfully run command without GUI

Expected Results:
a flag such as `--ignore-errors` that will give the CLI the power to bypass such errors


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
.
Comment 2 Michael Warner 2022-08-13 19:37:22 UTC
I believe you. Marking as NEW.
Comment 3 Mike Kaganski 2022-08-14 07:46:22 UTC
(In reply to Michael Warner from comment #2)
> I believe you. Marking as NEW.

Not opposed to the NEW status - but I fail to see how "I believe you" is a reason to mark anything as NEW by itself. The confirmation is expected to show that there is someone also having a similar issue, or who thinks it's a reasonable change/proposal, etc. It's not a matter of belief.