[cups.bugs] Jobs held using print via http

[Helge Blischke]

Michael R Sweet wrote:
> Adam O'Neill wrote:
> 
>> Hi,
>>
>> I have an educational client who is using a Windows 2003 AD print 
>> server. There is a requirement for users to print via http to this 
>> server providing an AD username and password for authentication.
>>
>> In OSX 10.4 the queue would be set up on each Mac as
>>
>> http://<print_server>/printers/<queue_name>/.printer
>>
>> the ppd provided and everything would print nicely with usage recorded 
>> by the provided AD username and password rather then the local osx 
>> account.
>>
>> On release of OSX 10.5 the same set up causes held jobs. A user will 
>> print, the job will be printed however the job will be held in the 
>> queue and the queue paused. This issue also appears in the latest 
>> distro's from Ubuntu etc.
>>
>> I thought I'd post here to see if this was a known issue or a config 
>> change is required as a quick search of the forums found nothing.
>>
>> Let me know what info I can provide to assist.
> 
> 
> This sounds like the same issue that John Hodrien recently reported.
> I suspect this is a compatibility issue between Windows and CUPS, and
> am working on it...
> 
> I've created STR #2682 to track this issue - please post your own
> experiences, log files, etc. there:
> 
>     http://www.cups.org/str.php
> 

This closely resembles an issue I recently had to fix for CUPS 1.3.5
(and had to before with several 1.1.x versions):

If you hook up a printer to CUPS by the IPP backend, and the respective
printer allows it's queues to be set up as "allow receiving" but "do not
(yet) print" the printer replies to the get-printer-attributes request
with a "paused" message (which gets translated to "printer offline" for
the printer state message).
This happens *after* the job has been successfully transferred, so the
printer has this job, but CUPS reacts with an internal STATE message
to the scheduler that causes the job to be held and the CUPS queue
stopped.

I fixed this by implementing an additional URI option but hesitate
to make this fix public, as my experience to this issue is restricted
to the Xerox' IPP implementation in their DocuSP software only.

But I could send you the modified backend/ipp.c source on request.

Helge


-- 
Helge Blischke
Softwareentwicklung

H.Blischke at acm.org