Bug 134430 - PDF Image inserted in document has wrong line colours when exported as PDF
Summary: PDF Image inserted in document has wrong line colours when exported as PDF
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
Version:
(earliest affected)
6.0.7.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: PDF-Export
  Show dependency treegraph
 
Reported: 2020-07-01 10:05 UTC by Stephan van den Akker
Modified: 2022-07-04 03:28 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Test PDF image produced in QGIS 3.14.0 (5.21 KB, application/pdf)
2020-07-01 10:05 UTC, Stephan van den Akker
Details
PDF result with first PDF inserted as image (4.48 KB, application/pdf)
2020-07-03 20:59 UTC, Roman Kuznetsov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan van den Akker 2020-07-01 10:05:06 UTC
Created attachment 162553 [details]
Test PDF image produced in QGIS 3.14.0

How to reproduce:
1: Insert PDF attachment#1 as image in document
2: Export document to PDF

Expected result:
- Line colours in exported PDF are identical to line colours in original document

Actual Result:
- All line colours in the exported PDF are black

The image was produced in QGIS version 3.14.0-Pi by exporting a "print layout" of some scratch vector map layers. PDF Export settings included "Always Export Text as Paths (Recommended)". The white lines surrounding the characters where created with the "text buffer" feature for layer labels.

Problem observed in:

Version: 6.4.3.2
Build ID: 1:6.4.3-0ubuntu0.20.04.1
CPU threads: 2; OS: Linux 5.4; UI render: default; VCL: gtk3; 
Locale: nl-NL (nl_NL.UTF-8); UI-Language: en-US
Calc: threaded

Version: 7.0.0.0.beta2
Build ID: 00(Build:0)
CPU threads: 8; OS: Linux 5.7; UI render: default; VCL: kf5
Locale: en-GB (en_GB.UTF-8); UI: en-GB
Calc: threaded

Version: 7.1.0.0.alpha0+
Build ID: c98affa44e3f61279ae9fe052dbcfbda0c58838e
CPU threads: 8; OS: Linux 5.7; UI render: default; VCL: kf5
Locale: en-GB (en_GB.UTF-8); UI: en-GB
Calc: threaded

More severe problem (everything black, not just the lines) observed in:

Versie: 6.0.7.3 (x64)
Build ID: dc89aa7a9eabfd848af146d5086077aeed2ae4a5
CPU-threads: 4; Besturingssysteem: Windows 10.0; UI-render: GL; 
Locale: nl-NL (nl_NL); Calc: group

Version: 6.0.7.3
Build ID: 1:6.0.7-0ubuntu0.18.04.10
CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); Calc: group
Comment 1 BogdanB 2020-07-01 10:11:41 UTC
I get an error when exporting to PDF.

"This page contains an error. It's possible that Acrobat it is not showing the image corectly."

In fact I have a blank page.


Tested on
Version: 6.4.4.2 (x64)
Build ID: 3d775be2011f3886db32dfd395a6a6d1ca2630ff
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: GL; VCL: win; 
Locale: ro-RO (ro_RO); UI-Language: en-US
Calc: threaded
Comment 2 Stephan van den Akker 2020-07-01 11:18:18 UTC
I can confirm your problem with Adobe Acrobat Reader DC 19.0.010.20098 on Windows 10. PDF-XChange viewer version 2.5 on Windows 10 displays a black-and-white image.

LO Draw 6.0 and Gimp 2.8 on the same system will import the exported PDF, but with the wrong line colours.
Comment 3 Roman Kuznetsov 2020-07-03 20:59:25 UTC
Created attachment 162623 [details]
PDF result with first PDF inserted as image

there is a problem with white borders aroud TEST word and with red border in triangle

Version: 7.0.0.1.0+
Build ID: 30ea3ba86b110db68c19815c5c67d4d315c091bf
Потоков ЦП: 4; ОС: Linux 5.5; Отрисовка ИП: по умолчанию; VCL: kf5
Locale: ru-RU (ru_RU.UTF-8); ИП: ru-RU
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:libreoffice-7-0, Time: 2020-07-03_04:42:21
Calc: threaded
Comment 4 Roman Kuznetsov 2020-07-03 21:02:40 UTC
but there is also difference between PDF readers! Look at PDF result from attach in Okular and in Firefox!

So I think it may be problem with SVG inside first Test PDF...
Comment 5 QA Administrators 2022-07-04 03:28:18 UTC
Dear Stephan van den Akker,

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