Bug 169105 - lpadmin complains about -p option
Summary: lpadmin complains about -p option
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: cups
Version: 3.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-09-23 02:04 UTC by Fredrick Meunier
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-09-23 08:50:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Fredrick Meunier 2005-09-23 02:04:31 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050720 Fedora/1.0.6-1.1.fc3 Firefox/1.0.6

Description of problem:
lpadmin seemed to work OK when I first installed RHEL3, but these days I get the following on all sorts of commands (but not a simple /usr/sbin/lpadmin p level5printer):

# /usr/sbin/lpadmin p level5printer -E
lpadmin: Unknown argument 'p'!


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

How reproducible:
Always

Steps to Reproduce:
1. Install CUPS printer
2. Run /usr/sbin/lpadmin -P <my printer> -E
  

Actual Results:  See error message about unknown argument

Expected Results:  Print queue should be enabled, no error about unknown argument '-p'

Additional info:

Comment 1 Tim Waugh 2005-09-23 08:39:47 UTC
It sounds like it isn't actually a dash (-) before the 'p' -- perhaps your
keyboard mapping doesn't match your keyboard layout?

If you paste this in to a terminal, does it give the results you expect?:

/usr/sbin/lpadmin -p level5printer -E


Comment 2 Fredrick Meunier 2005-09-23 08:50:40 UTC
Having quit my gnome-term and restarted my problems have now gone. I note that
my copy and paste above no longer looks like a dash either now I have restarted
Firefox.

Thanks for your help (and I can't believe that was the problem!).


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