Bug 191997

Description of problem:
New CUPS fails to print to a known good IPP printer in most circumstances

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

How reproducible:
Always

Steps to Reproduce:
1. send a job to printer from any app except: a) test page from
system-config-printer, or b) a2ps. I.E. Try to print from acroread, firefox,
thunderbird, man -t | lpr, ...,  etc.

2.
3.
  
Actual results:
Nothing gets printed, cups reports:

(/usr/lib/cups/backend/ipp) stopped with status 1

and stops queue

Expected results:
something prints & cups leaves queue turned on

Additional info:
After yum upgrade this morning printing stopped working.

I am printing using IPP to a Xerox Phaser 8400DP. The failure happens using the
PPD file from Xerox's support site, imported into cups. I have been using this
PPD and identical configuration of CUPS for over two years, since FC3 and its
old version of cups. It also occurs using the CUPS generic PostScript driver,
which has also worked in the past.

Based on past experience, I removed the printer from my CUPS configuration and
restarted the cups service, then, using system-config-printer, imported the
Xerox supplied PPD file, and finally added the printer. I have also edited the
CUPS config to use generic Postscript driver with the same results.

To eliminate  as much variation as possible, I've used the results from
man -t cupsd.conf | lpr
as my failure test case. Directing the output of man -t to a file and then
netcat-ing it directly to port 9100 of the printer does print, but this doesn't
allow me access to any of the features of the printer.

I have turned on debugging in /etc/cupsd.conf and captured both the CUPS logs
and network traffic (using ethereal) corresponding to a) successful printing
using the command "a2ps .sig.pub" and b) the typical, unsuccessful printing
using "man -t cupsd.conf | lpr". I will attach an excerpt from the (not very
revealing) /var/log/cups/error_log, and subsequently the mush more revealing
packet captures.