Bug 71654 - LO never remember color settings for my printer
Summary: LO never remember color settings for my printer
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
Version:
(earliest affected)
4.1.3.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-15 17:50 UTC by Thierry Vignaud
Modified: 2014-08-10 15:43 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thierry Vignaud 2013-11-15 17:50:10 UTC 
Unlike other apps (eg: firefox, evince), LO never remember color settings for my printer.
He kept defaulting all my printing jobs to color whereas I want to print in b&w by default.
Comment 1 bfoman (inactive) 2013-11-15 20:09:15 UTC 
Please be more precise in you bug reports and check out the following pages before adding more details about your printer and system:
https://wiki.documentfoundation.org/BugReport
https://wiki.documentfoundation.org/QA/BugReport/Printing
Comment 2 Joel Madero 2014-07-21 04:50:02 UTC 
Setting to NEEDINFO as the user has not provided the information requested by bfoman

@Thierry - if you can still reproduce this please provide more information about your system and your version of LibreOffice and Printer and set to UNCONFIRMED. Thanks!
Comment 3 Thierry Vignaud 2014-08-10 07:29:42 UTC 
This was with an HP OfficeJet Pro 8600 on Mageia Linux.
It looks fixed as of LO-4.3
Comment 4 Thierry Vignaud 2014-08-10 12:32:48 UTC 
That's not the proper resolution.
Color settings wasn't remembered in LO-4.1 whereas it got fixed in the mean time either in 4.2 or in 4.3
Comment 5 QA Administrators 2014-08-10 15:43:28 UTC 
WORKSFORME is the correct status. WORKSFORME applies with two cases:

1. Can't repro the original reporters issue
2. The problem is resolved in a later version but we have no clue what exact commit fixed it.


RESOLVED -> Fixed is only when we know the exact commit. Changing to WORKSFORME