Created attachment 158798 [details]
source odf document
I have recently upgraded from LibreOffice 5.4 to 6.2. When we convert a .odf document to PDF a blank page is getting appended in some circumstances. The blank page does not have a footer on it where we have a footer defined for the document. With version 5.4 we do not see this behavior.
The environment in use is
JODConverter with local manager
LibreOffice is used to convert from .odf to .pdf
LibreOffice 5.4.5 run with an Alpine AWS image (3.7)
LibreOffice 6.2 run with an Ubuntu AWS image (Xenial)
Have tested on OSX with LibreOffice 6.6 - No blank page after export
Created attachment 158799 [details]
source odf for export in LO 5.4
Created attachment 158800 [details]
pdf exported with LO 5.4
Created attachment 158801 [details]
source odf for export in LO 6.2
Created attachment 158802 [details]
pdf exported with LO 6.2
I can't repro with the source odf document and
Version: 18.104.22.168 (x64)
Build ID: 4e471d8c02c9c90f512f7f9ead8875b57fcb1ec3
CPU threads: 4; OS: Windows 10.0 Build 19582; UI render: GL; VCL: win;
Locale: es-ES (es_ES); UI-Language: en-US Calc: CL
(In reply to Andy Lanzer from comment #0)
> Have tested on OSX with LibreOffice 6.6 - No blank page after export
Please explain what you meabt by 6.6.
Did you test master version 7.0+?
How do you convert, via GUI or with headless?
(In reply to Timur from comment #6)
> (In reply to Andy Lanzer from comment #0)
> > Have tested on OSX with LibreOffice 6.6 - No blank page after export
> Please explain what you meabt by 6.6.
> Did you test master version 7.0+?
> How do you convert, via GUI or with headless?
I am running the convert headless.
The version I tested on OSX is 6.2.8 (sorry out the incorrect initial )
The environment where the issue occurs is a Docker container deployed to an AWS fargate ecs container.
The application is SpringBoot, JODConverter, and LibreOffice
Have not tested with master version 7.0.
Due to company policies I am limited to the version of images I am able to build and run with. I am not able to use an Ubuntu image which support version 7.
Bug needs to be confirmed with master by QA. Based on what reporter wrote, likely a regression. Could be a duplicate of bug https://bugs.documentfoundation.org/show_bug.cgi?id=116924, but image issue and beginning version (that's not clear there) should be checked first.
Created attachment 158828 [details]
ODF 1 page
There are multiple issues here:
1. Both ODF attachment 158799 [details] and attachment 158801 [details] (should be the same) open as 2 pages in LO 6.2 and 5.4.
I don't know how PDF attachment 158800 [details] from LO 5.4 fits to 1 page. Please explain what happens to the missing "Your discounts" table.
We cannot test with those.
2. If we delete "Your discounts" table, we have 1 page ODF in 6.2.
That file, which I attach here, needs be tested headless in 5.4 and 6.2 Lin. Please confirm if that one saves as 1 or 2 pages PDF for you.
Both Win and Lin need be tested. I now have Win headless but crashes on this file for 5.4 and 6.2 and master that works is not enough.
3. In the meantime, starting from master 7.0+ this 1 page ODF opens as 2 pages on a system without Roboto font. Opens 1 page if installed.
That would be a separate bug for Roboto replacement. I note for QA who would test.
Created attachment 158829 [details]
ODF 1 page compared LO 5.4 and LO 7.0+
This is a screenshot for issue 3, not part of this bug, but important for testing.
The Your Discounts table are hidden and should not be printed.
BTW - I am trying to get the app we use to run locally in a docker container. Not done yet but will keep you up to date on my progress
[Automated Action] NeedInfo-To-Unconfirmed
I have been able to recreate the issue locally on my mac.
The results I am seeing are
5.x 1 page 1 page
6.1.x 1 page 1 page
6.2.x 2 pages 2 pages
6.3.x Not tested 2 pages
6.4.x Not tested. 2 pages
Does not seem to be Ubuntu specific.
The change in behavior is between 6.1.x and 6.2.x
Can I get some-one to look at the most reecent information that I to this ticket.
I tried headless in Mint 19 with LO 6.1 up to 7.0+ and couldn't confirm, always 1 page in PDF.
Note: you may try instdir/program/soffice --pt PDF to print to CUPS PDF.
This issue only occurs when the conversion is invoked through the API, Java in my case. Have not seen this through the LO application or through running it headless.
(In reply to Andy Lanzer from comment #17)
> This issue only occurs when the conversion is invoked through the API, Java
> in my case. Have not seen this through the LO application or through
> running it headless.
So please include full instructions and code to reproduce.
Also, you can bisect this regression yourself: https://wiki.documentfoundation.org/QA/Bibisect
Dear Andy Lanzer,
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
Dear Andy Lanzer,
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