Used LO Writer to compose document and inserted PDF image file into Writer ODT file. When ODT file was exported to PDF image was not visible in PDF file produced.
LO 22.214.171.124 installed to Ubuntu 18.04 LTS.
First reported at LO support forums:
Reporting this at Mike Kaganski's request.
Steps to Reproduce:
1.Compose document using LO Writer 126.96.36.199.
2.Scan image, edit, crop, save to PDF.
3.Insert image to composed doc.
4.Save doc to ODT file.Image visible in document.
5.Export doc to PDF. Image not visible in PDF file.
Image not visible when ODT file exported to PDF file.
Expected image to be visible in exported PDF file.
User Profile Reset: No
The software should have exported ODT file to PDF and included the embedded PDF file.
Created attachment 154188 [details]
sample ODT file with PDF embedded
Created attachment 154189 [details]
sample exported PDF file, embedded image not visible
Scanner software used was gscan2pdf 2.1.0. Used it to scan and then crop image to desired size. Saved as PDF from gscan2pdf.
Unzipping, there are two .PNG images held in the ODT archive's Pictures directory--no PDF.
Maybe not the correct ample document attachment? Or are the scanned imaged really PDF? PNG maybe?
And as noted on Ask thread, on Windows builds Print preview, and Export to PDF do show the signature frame.
Created attachment 154204 [details]
pdf image file
Created attachment 154205 [details]
2nd sample ODT with PDF embedded
Created attachment 154206 [details]
2nd sample exported PDF, embedded image not visible
On my Ubuntu 18.04 LTS system I used the following PDF viewing software:
Document Viewer 3.28.4
Embedded PDF image not visible in exported PDF in either software.
(In reply to xiphoid from comment #6)
> Created attachment 154205 [details]
> 2nd sample ODT with PDF embedded
Again, there is no embedded PDF. They are PNG, and the content.xml lists the image frame as image/x-vclgraphic; not sure if there is an issue embedding PDF between Linux <--> Windows
If I replicate the "signature" using the PDF on Windows build of 188.8.131.52 I get the this stanza in content.xml --
<draw:frame draw:style-name="fr1" draw:name="Image1" text:anchor-type="paragraph" svg:x="0.0409in" svg:y="0.1043in" svg:width="1.7398in" svg:height="0.5835in" draw:z-index="0"><draw:image xlink:href="Pictures/10000000000000A700000038F8C2CA3E3C57B71F.pdf" xlink:type="simple" xlink:show="embed" xlink:actuate="onLoad" loext:mime-type="application/pdf"/><draw:image xlink:href="Pictures/10000000000000A7000000383AAC44F45A8C3941.png" xlink:type="simple" xlink:show="embed" xlink:actuate="onLoad" loext:mime-type="image/png"/></draw:frame>
And the pictures directory of the ODF archive holds both the PDF and the PNG frame. Something is not behaving with your Linux build.
Created attachment 154207 [details]
sample document assembled on Windows build 184.108.40.206 with PDF actually embedded
My sample files were created using LO 220.127.116.11 on Ubuntu GNU/linux. You are examining them using LO 18.104.22.168 on Win. That is not exactly the kind apples-with-apples comparison needed to verify the bug. Also, the file you uploaded is an ODT file, not exported PDF containing embedded PDF image. Not sure what you are trying to illustrate with it.
Do you suggest that my Ubuntu GNU/linux build is not behaving with LO? Or that LO 22.214.171.124 is playing up?
LO 126.96.36.199 was installed via system upgrade from Ubuntu 16.04 LTS to 18.04 LTS. I would guess 188.8.131.52 is integrated in the Ubuntu distro ISO file. My system is regularly updated and would have the latest LO version supplied by Cannonical installed.
I haven't changed any LO settings on my system. It is running default settings.
Anyway, I am fortunate there are alternative methods to achieve the embedded image result I desire.
(In reply to xiphoid from comment #11)
> My sample files were created using LO 184.108.40.206 on Ubuntu GNU/linux. You are
> examining them using LO 220.127.116.11 on Win. That is not exactly the kind
> apples-with-apples comparison needed to verify the bug. Also, the file you
> uploaded is an ODT file, not exported PDF containing embedded PDF image. Not
> sure what you are trying to illustrate with it.
No, as appropriate I am examining them by unzipping the ODF archive and looking at content the constituent XML and files.
> Do you suggest that my Ubuntu GNU/linux build is not behaving with LO? Or
> that LO 18.104.22.168 is playing up?
Simply saying your Linux system is _not_ embedding PDF into the ODF archive. While on a Windows build recent master and 22.214.171.124 it does. Not sure what to make of it...
A couple of days ago I downloaded an AppImage of LO 126.96.36.199. AppImages have software bundled up in a no-install package, similar to portable apps for Win environment.
AppImage used was LO 188.8.131.52 fresh standard.
I made additional sample documents using the same processes as done with LO 184.108.40.206. The result was the same: embedded PDF image does not display when ODT file exported as PDF.
Created attachment 154303 [details]
sample ODT made with LO Writer 220.127.116.11 appimage
Created attachment 154304 [details]
sample exported PDF, embedded PDF img not visible, LO 18.104.22.168
Created attachment 154306 [details]
Extracted from attachment 154303 [details] the scanned PDF that will not render into exported PDF
OK, with attachment 154303 [details] ODF archive I now see an embedded PDF. And, an Export to PDF from Writer produces a PDF that will not show the image.
Creating a new document and inserting the extracted PDF as an image likewise will not show the extracted PDF when new document is exported.
Windows 10 Home 64-bit en-US (1903) with
Version: 22.214.171.124 (x64)
Build ID: b79626edf0065ac373bd1df5c28bd630b4424273
CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win;
Locale: en-US (en_US); UI-Language: en-US
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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!