Bug 91334 - printconf-gui doesn't change ~home/.lpoptions default
Summary: printconf-gui doesn't change ~home/.lpoptions default
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: printconf   
(Show other bugs)
Version: 9
Hardware: All Linux
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2003-05-21 15:23 UTC by Hardy Merrill
Modified: 2007-04-18 16:53 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-05-21 15:30:03 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Hardy Merrill 2003-05-21 15:23:05 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
When I use printconf-gui to change my default printer, it sets it fine and
printing a test page to the new default printer works.

*BUT*, while still logged in to same account, using 'lpr somefile' right after
changing the default printer prints to the *old* default printer.

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

How reproducible:

Steps to Reproduce:
1. Use printconf-gui (Main Menu / System Settings / Printing) to
   change default printer.
2. Apply change
3. Quit printconf-gui
4. lpr somefile

Actual Results:  still prints to *old* default

Expected Results:  should print to *new* default printer

Additional info:

A workaround was to manually change the .lpoptions file in my home directory.

I had to add these lines:
Dest newprinter
Default newprinter

and then my 'lpr somefile' printed on my *new* default printer.

Comment 1 Tim Waugh 2003-05-21 15:30:03 UTC
Redhat-config-printer, being a system tool (and needing to run as root), sets
the *system* default not the user default.  Use the Print manager (in
Accessories) to change your user default.

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