Bug 139771 - FILEOPEN PDF: Importing results in empty pages on some pdf files (testfile included)
Summary: FILEOPEN PDF: Importing results in empty pages on some pdf files (testfile in...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
7.0.3.1 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: PDF-Import-Draw
  Show dependency treegraph
 
Reported: 2021-01-19 21:06 UTC by Luke
Modified: 2025-02-16 03:10 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Testfile which imports as blanks (21.88 MB, application/pdf)
2021-01-19 21:08 UTC, Luke
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Luke 2021-01-19 21:06:23 UTC
Description:
On some pdf files draw imports just blank (white) images instead of the pdf content. 
I found a file available on the web that can be used to reconstruct the bug; unfortunately I didn't saved the links so I appended the file


Steps to Reproduce:
1. Open a pdf file:
2. either in the file explorer via right click -> open as -> open office
3. or by opening draw, then go to file->open->select pdf file

Actual Results:
Openoffice may read it correctly or may just create empty (white) pages depending on the file. Most files read correct.

Expected Results:
Proper import of the pdf file with readable, really imported content


Reproducible: Always


User Profile Reset: No



Additional Info:
It seems to depend on the internals of the pdf file.
Also filed in anoter bug report with a somewhat related problem which also leads to trouble on a converted version of this file
Comment 1 Luke 2021-01-19 21:08:15 UTC
Created attachment 169026 [details]
Testfile which imports as blanks
Comment 2 mulla.tasanim 2021-01-20 16:53:17 UTC
Thank you for reporting the bug.

It opens only empty pages, also takes longer to open pdf in LO

I can confirm the bug present in

Version: 7.0.3.1 (x64)
Build ID: d7547858d014d4cf69878db179d326fc3483e082
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL

Version: 7.2.0.0.alpha0+ (x64)
Build ID: 761a672d62df1891b9f4f367a499b220ab2b33fa
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL
Comment 3 QA Administrators 2023-01-21 03:23:59 UTC Comment hidden (obsolete)
Comment 4 Luke 2023-02-16 17:38:25 UTC
I can confirm the Bug is still present in 

Version: 7.5.0.3 (X86_64) / LibreOffice Community
Build ID: c21113d003cd3efa8c53188764377a8272d9d6de
CPU threads: 16; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win
Locale: de-DE (de_DE); UI: de-DE
Calc: CL threaded
Comment 5 QA Administrators 2025-02-16 03:10:20 UTC
Dear Luke,

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

MassPing-UntouchedBug