Download it now!
Bug 106484 - UI: Print Properties Device tab dropdown items not applied or remembered
Summary: UI: Print Properties Device tab dropdown items not applied or remembered
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
(earliest affected) release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
Keywords: bibisectRequest, regression
Depends on:
Blocks: Printer-Settings Print-Dialog
  Show dependency treegraph
Reported: 2017-03-10 20:38 UTC by tmacalp
Modified: 2021-01-24 04:05 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description tmacalp 2017-03-10 20:38:19 UTC
Attempting to change items at the bottom of the Print Properties Device tab, such as "Printer language type," "Color," or "Color depth" are completely ignored and remain unset after clicking OK.

I found this testing old bugs relating to PostScript vs PDF Mode printing.  It turns out that as of LO 5.0, this bug keeps these settings from being applied.

Steps to Reproduce:
1. New document/drawing/spreadsheet/etc...
2. File->Print
3. Click Properties
4. Select "Device" tab
5. Change "Printer language type" to something else
6. OK
7. Click Properties
8. Select "Device" tab again.

Actual Results:  
The Printer language type was never actually set, so it will return to its original value.  Printing after clicking OK will generate a print job that does not have the settings applied.

Expected Results:
The Printer language type should be set to whatever we changed it to, as it used to.  

Reproducible: Always

User Profile Reset: Yes, fresh profile.

Additional Info:
LibreOffice refuses to set any 3 of these drop-down items ("Printer language type," "Color," and "Color depth").  It's not that these items are applied but not remembered.  Attempting to set these items will affect the print job.  This could cause someone to accidentally print a huge job in color and potentially waste a lot of money.  Note that I believe there is a bug with pdf mode printing where attempting to change the print job to grayscale by using the Color dropdown will be ignored.  It only works under PostScript printing.

LibreOffice appears to honor the global setting for either PDF Mode or Postscript level from driver (Tools->Options->Print->PDF as standard print job format).

One workaround is that if an item is selected in the Device tab main list like Media Type (or whatever options your printer offers), the drop-down setting will then be applied/remembered.  My guess is there is problem with the logic for determining when a setting has been modified and will need to be saved/applied.

This affects LO 5.0.0+ but not 4.4.7.  I wasn't sure if this would fall under UI or Printing. 

User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0
Comment 1 Xisco Faulí 2017-03-14 09:06:23 UTC
Confirmed in

Build ID: 5b168b3fa568e48e795234dc5fa454bf24c9805e
CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; 
Locale: ca-ES (ca_ES.UTF-8)

but not in

Build ID: 0db96caf0fcce09b87621c11b584a6d81cc7df86
Locale: ca-ES (ca_ES.UTF-8)
Comment 2 QA Administrators 2018-03-15 03:38:20 UTC Comment hidden (obsolete)
Comment 3 Buovjaga 2018-06-02 15:12:29 UTC
Still repro and this seems to be Linux-only as Windows offers the dialog of the printer driver itself.

Arch Linux 64-bit
Build ID: 8e63d451b2aeb646ece98c4e219f92957f4482bd
CPU threads: 8; OS: Linux 4.16; UI render: default; VCL: kde4; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group threaded
Built on June 1st 2018
Comment 4 Xisco Faulí 2019-01-24 13:14:20 UTC
Still reproducible with the new print dialog

Build ID: 0d46fb02f3f19d11db40b6c5335d78a3894502d7
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US
Calc: threaded

@Daniel Silva, I thought you might be interested in this issue...
Comment 5 QA Administrators 2021-01-24 04:05:30 UTC
Dear tmacalp,

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

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

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:

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team