Bug 97392 - -convert-to does not work for password-protected files
Summary: -convert-to does not work for password-protected files
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: filters and storage (show other bugs)
(earliest affected) release
Hardware: All All
: medium minor
Assignee: Not Assigned
Depends on:
Blocks: Commandline
  Show dependency treegraph
Reported: 2016-01-27 12:48 UTC by Thomas Seeling
Modified: 2024-03-30 03:14 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Seeling 2016-01-27 12:48:04 UTC
I can convert normal files on the command line but conversion fails for password-protected files.
I'd like to see some kind of option to provide the password for the file.

libreoffice -env:UserInstallation=file:///tmp/lo-tmp.$$ --headless --convert-to html test.ods

silently does *nothing*. Not even an error message that a protected file can't be converted.
Comment 1 Buovjaga 2016-01-28 17:23:39 UTC
Sounds like a fair request.
Comment 2 QA Administrators 2017-03-06 13:44:24 UTC Comment hidden (obsolete)
Comment 3 Thomas Seeling 2017-03-06 14:12:22 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2018-03-07 03:41:57 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2020-03-07 03:19:18 UTC Comment hidden (obsolete)
Comment 6 Thomas Seeling 2020-03-07 11:43:58 UTC
RHEL 7.7, Libreoffice
Bug is still present but at least it gives an error message now.
Message is not reporting actual problem, but it's an improvement.

Error: source file could not be loaded

Command used to test:

scalc -env:UserInstallation=file:///tmp/lo-tmp.$$ --headless --convert-to html test.ods
Comment 7 QA Administrators 2022-03-08 03:44:45 UTC Comment hidden (obsolete)
Comment 8 Timur 2022-03-30 15:09:59 UTC
Repro 7.4+. As in bug 148253, I note that failed convert should give error status that is not 0.
Comment 9 QA Administrators 2024-03-30 03:14:24 UTC
Dear Thomas Seeling,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team