Bug 216152 - OutputBin option via lpd is failing
Summary: OutputBin option via lpd is failing
Keywords:
Status: CLOSED DUPLICATE of bug 216154
Alias: None
Product: Fedora
Classification: Fedora
Component: cups
Version: 5
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-11-17 15:27 UTC by Steve Hanselman
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-11-17 15:33:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
tcpdump capture of the generated postscript (150.54 KB, application/octet-stream)
2006-11-17 15:27 UTC, Steve Hanselman
no flags Details

Description Steve Hanselman 2006-11-17 15:27:54 UTC
Description of problem:

(presumably) following an update fo cups the ability to specify certain options 
via lpd is now failing.


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

1.2.5

How reproducible:

Always fails now

Steps to Reproduce:
An example would be as follows:-
  fax2ps -H11.5 -W8.25 -S ../recvq/fax000000825.tif |lpr -P sales_laser -o 
OutputBin=Left -o InputSlot=Tray2

However, the following works, so it is specific to an option rather than all 
options (actually, I could be wrong, it could just be that the printer ignores 
the error rather than dying on the job as it does for outputbin) :-
fax2ps -H11.5 -W8.25 -S ../recvq/fax000000825.tif |lpr -P sales_laser -o 
InputSlot=Tray2

Actual results:
postscript job is rejected by printer and no output is produced

Expected results:
Job will run and produce output, tyaking paper fromt he specified bin and 
placing in the specified output tray.


Additional info:

Comment 1 Steve Hanselman 2006-11-17 15:27:54 UTC
Created attachment 141481 [details]
tcpdump capture of the generated postscript

Comment 2 Tim Waugh 2006-11-17 15:33:49 UTC

*** This bug has been marked as a duplicate of 216154 ***


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