Bug 33780 - PRINTING printer driver settings have strange defaults which can't be changed (eg color, print quality)
Summary: PRINTING printer driver settings have strange defaults which can't be changed...
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
3.3.0 release
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2011-01-31 13:00 UTC by Tim Richardson
Modified: 2011-02-01 13:12 UTC (History)
0 users

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 Tim Richardson 2011-01-31 13:00:19 UTC
Libreoffice 3.3  on Debian sid. Using CUPS printing.
I have an HP OfficeJet pro.
When I go to print, I must choose Properties and then Device to reset Output Mode back to Color.
("strange defaults" in the summary of this bug means "I don't know where the default setting is coming from").
It is defaulting the High Quality Greyscale (the first option). The default for this printer in CUPS is color.
And I have to do this every time; it resets back to High Quality Greyscale. Apart from choosing a correct default, I would also like it to preserve my most recently used setting, but it doesn't. 

What I expect is that 
* the defaults come from the CUPS defaults for the printer. Or if I change values in File -> Printer Settings... they are used in the print dialog (they are not, at least as far as the Output Mode settings goes).
* most-recent changes are preserved at least for the currently opened documents.

I think this is a regression, I don't remember this problem with 3.2.
Comment 1 Tim Richardson 2011-01-31 15:18:12 UTC
In fact, this may be a CUPS bug. There is HP printer configuration software (HPLIP) which for some reason had an output setting of High Quality Greyscale. 
This is picked up by Libreoffice, but not by the CUPS admin interface.

Changing the setting in HP LIP, and restarting LibreOffice, seems to work.
I'll give myself a day of use to make sure of this, then I will close the bug as invalid.