Bug 148420 - imported scans went white after calling export to pdf
Summary: imported scans went white after calling export to pdf
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
Version:
(earliest affected)
3.3.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-04-06 11:07 UTC by Rikkit
Modified: 2022-11-21 03:32 UTC (History)
2 users (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 Rikkit 2022-04-06 11:07:06 UTC
Description:
I have a .odt file with 3 imported pdf-scans inside.
When I open it in Libreoffice Writer it seems all fine.
But as soon as I call the "export to pdf" function 2 of those imported pdf turn all white.
These 2 have been cropped, and resized.
When I open the created pdf only the last page is completly white.

When I reopen the .odt file the content of all pages is rendered as normal again.

Using the Microsoft-Pdf-writer creates a "flawless" pdf, but would prefer to have a "tagged pdf"

Steps to Reproduce:
0. import a DIN A4 pdf-scan into a new writer doc.
1. import a DIN A3 pdf-scan
2. crop it, to only show only one DIN A4 side
3. resize and move it to fill out a new DIN A4 page
4. repeat step 1 -3 for the other half of the DIN A3 page
5. call "export to pdf"


Actual Results:
The cropped and resized scans (page 2 & 3) are now rendered all white in Libre office writer


when you open the new exported pdf file Page 3 is rendered all white

Expected Results:
No changes at all to the Document in Libre Office Writer

Having all imported scans visible in the exported pdf


Reproducible: Always


User Profile Reset: Yes



Additional Info:
When you save and reopen the .odt file, the previusly white scans are rendered normaly again, until you call export to pdf again.

Using the "Microsoft to pdf" printer creates a "flawless" pdf, sadly it doesen't support the "tagging"- feature (creating a linked index based of Heading-formation)

This has been performed on a fresh install of 3.3.2
This issue persisted when repeating it with safe mode enabled
Comment 1 raal 2022-04-23 12:03:12 UTC
Hello,

Thank you for filing the bug. Please send us a sample document, as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO', so please do change it back to 'UNCONFIRMED' once you have attached a document.
(Please note that the attachment will be public, remove any sensitive information before attaching it.)
How can I eliminate confidential data from a sample document?
https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F

Also update your installation of LO and retest. Version 3.3.2 is old.
Thank you
Comment 2 QA Administrators 2022-10-21 03:45:49 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2022-11-21 03:32:24 UTC
Dear Rikkit,

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