Bug 117265 - PDF export in Draw uses the "document background" application color in PDF export
Summary: PDF export in Draw uses the "document background" application color in PDF ex...
Status: RESOLVED DUPLICATE of bug 38065
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
Version:
(earliest affected)
3.5.0 release
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Document-Colors-Palette
  Show dependency treegraph
 
Reported: 2018-04-27 03:57 UTC by Kenneth Hanson
Modified: 2020-06-19 15:39 UTC (History)
1 user (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 Kenneth Hanson 2018-04-27 03:57:12 UTC
Description:
I noticed this when black and white drawing that I printed from an exported PDF had a light grey background. It turns out that LO Draw is incorrectly using the "document background" from Options > LibreOffice > Application Colors.

I had previous set this color to a light gray in Writier to avoid eyestrain, and to confirm I set the background to purple. The background comes out purple in PDF export in Draw, as well as Impress.

Printing from Draw is not affected. PDF export in Writer and Calc is not affected.

Steps to Reproduce:
1. Set application color "document background" to something other than "default".
2. Export to PDF.

Actual Results:  
PDF background color is changed.

Expected Results:
PDF background colod is unaffected.


Reproducible: Always


User Profile Reset: No



Additional Info:


User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0
Comment 1 Buovjaga 2018-05-23 14:00:42 UTC
Repro. Looks like this has always been this way.

Arch Linux 64-bit
Version: 6.1.0.0.alpha1+
Build ID: 5956828c88501ef1366e60010b05053a8e1e642e
CPU threads: 8; OS: Linux 4.16; UI render: default; VCL: kde4; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on May 23rd 2018

Win 10
3.5.0
Comment 2 QA Administrators 2019-05-24 02:56:51 UTC Comment hidden (obsolete)
Comment 3 Kenneth Hanson 2019-11-02 03:18:46 UTC
No change as of v6.3.2.2.
Comment 4 Kenneth Hanson 2020-04-01 01:49:45 UTC
Bug still present in v6.4.2.2.
Comment 6 Buovjaga 2020-06-19 15:39:04 UTC

*** This bug has been marked as a duplicate of bug 38065 ***