Bug 156148 - Unattended Windows command line convert (headless) has inconsistant results
Summary: Unattended Windows command line convert (headless) has inconsistant results
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.5.4.2 release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-07-03 21:34 UTC by michael
Modified: 2024-02-15 03:12 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description michael 2023-07-03 21:34:55 UTC
Description:
Headless converting files from local keyboard & mouse is perfect and amazing *but* from an internet or WAN script LO fails to convert some document types without issuing an error.

Steps to Reproduce:
Windows 11 pro

1.Web page using CGI-BIN script that issues command line to convert RTF document to DOC file is always successful.  Example that works fine:
  
c:\libreoffice\program\soffice --headless --convert-to doc --outdir . file.rtf

2.Same Web page and scripts to issue command line to convert RTF document to PDF or ODT documents always fails.
  
c:\libreoffice\program\soffice --headless --convert-to pdf --outdir . file.rtf
c:\libreoffice\program\soffice --headless --convert-to odt --outdir . file.rtf

3.All the scripts above executed by local user keyboard are successful. 

Actual Results:
1. Create web page link so user can convert and download documents remotely.
2. Create script to convert RTF document to DOC.
3. Observe that the conversion from RTF to DOC is successful.
4. Modify script (step 2) to convert RTF to PDF or ODT.
5. Observe that that document conversions failed.
6. Observe that user can issue all command lines from keyboard successfully.

Expected Results:
Converting from RTF to DOC is successful so permissions, locations, and syntax are correct.
Converting from RTF to PDF or ODT expected to have same success but fail without an error.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
It would be great to convert files on-demand, remotely and unattended (!) using windows. I tested this on Debian Linux (non-production) and same script produces DOC/PDF/ODT perfectly using LO.  Because of LO's conversion of RTF to DOC is successful on Windows it may be PDF/ODT conversions are a Windows environment issue that LO cannot handle.
Comment 1 Stéphane Guillou (stragu) 2023-07-18 09:48:27 UTC
- Does this happen with all RTF files or only (a) specific document(s)? If only with some, please attach an example document.
- Do you have the same issue with previous versions of LibreOffice?
- Please check that this is not a network or browser limitation.
- As this requires some effort setting up an environment to reproduce the issue, please provide as many scripts as possible to make it easier for contributors.
Comment 2 QA Administrators 2024-01-15 03:11:59 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2024-02-15 03:12:47 UTC
Dear michael,

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