Bug 509064 - libgnomecups checks for cups lpoptions in the wrong place
Summary: libgnomecups checks for cups lpoptions in the wrong place
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: libgnomecups
Version: 5.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Marek Kašík
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On: 509066 603809
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-01 05:48 UTC by ritz
Modified: 2018-10-27 14:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 246602
Environment:
Last Closed: 2009-11-11 09:22:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
patch based on upstream code (408 bytes, patch)
2009-07-01 06:12 UTC, ritz
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2009:1577 0 normal SHIPPED_LIVE libgnomecups bug fix update 2009-11-11 09:22:03 UTC

Description ritz 2009-07-01 05:48:58 UTC
+++ This bug was initially created as a clone of Bug #246602 +++

Description of problem:

For cups 1.2 the default user specific queue options are written to
~/.cups/lpoptions. libgnomecups only checks the old ~/.lpoptions location.

This problem was also discovered & fixed in Ubuntu, bug #34112. The patch
attached is an extract from the one by Martin Pitt in that bug.

Version-Release number of selected component (if applicable):

libgnomecups-0.2.2-8.x86_64

Additional info:
Note that libgnomecups doesn't even honor any lpoptions by default; for that the
patch in bug 157878 is needed.


Created an attachment (id=158430)
also check ~/.cups/lpoptions for CUPS options

Comment 2 ritz 2009-07-01 06:12:10 UTC
Created attachment 350059 [details]
patch based on upstream code

Comment 4 Marek Kašík 2009-11-03 15:38:52 UTC
I committed the patch from the comment #2. The build is libgnomecups-0.2.2-9.

Marek

Comment 8 errata-xmlrpc 2009-11-11 09:22:07 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-1577.html


Note You need to log in before you can comment on or make changes to this bug.