[cups.general] CUPS 1.3.6, Linksys PSUS4, jobs never complete

[Ace]

Michael R Sweet wrote:

> Ace wrote:
>> Michael R Sweet wrote:
>> 
>>> Ace wrote:
>>>> Ace wrote:
>>>>
>>>>> L.S.
>>>>>
>>>>>
>>>>> I recently decoupled my printer from a desktop computer in an effort
>>>>> to simplify things for the other networked computers, i.e. not having
>>>>> to keep one machine running just for a printer..
>>>>> I deleted the printer from CUPS and re-set up the printer with IPP URL
>>>>> and the same driver it used when it was still connected directly by
>>>>> USB.
>>>>>
>>>>> Mandriva 2008 Free + CUPS 1.3.6 => Linksys PSUS4 fw1.1 via IPP => hp
>>>>> photosmart 7350 colour printer.
>>>>>
>>>>> The driver used is named "HP PhotoSmart 7350 Foomatic/hpijs
>>>>> (recommended)".
>>>>>
>>>>> In the above, CUPS connects to the PSUS4 via IPP to the printer.
>>>>> What happens is, I can print 1 job from this Linux machine.
>>>>> After that, I can't do anything, because the first job never
>>>>> completes, it is 'stuck' in the processing queue indefinitely and the
>>>>> printer will forever show as 'processing..., accepting jobs'.
>>>>>
>>>>> If I print from a Windows machine, everything is fine.
>>>>> So i'm assuming something needs to be done inside CUPS.
>>>>>
>>>>> Any ideas would be appreciated!
>>>> Pretty please? :)
>>> The Linksys implementation has been broken for a long time.  You can
>>> report the problem to them or use an alternate protocol (LPD or
>>> socket on port 4010 is the usual path...)
>>>
>> Hmm, that sorta kinda doesn't explain it though..
> 
> Windows doesn't implement IPP/1.1, and doesn't require printers to
> actually support most of the IPP spec.
> 

Users are not supposed to know about undocumented 'features' such as that..
(And this user did not know, until now)

I got fed up and reset the printer configuration in CUPS, this could no
longer wait till another weekend to fix.

CUPS now shows:
Printer Driver: HP PhotoSmart 7350 Foomatic/hpijs (recommended)
Printer State: idle, accepting jobs, published.
Device URI: lpd://192.168.3.2/L1

You'll notice I changed the URI to lpd. CUPS now prints to the device as it
should, jobs are spooled and immediately printed, and the jobs complete as
far as I can tell (they disappear from the queue without error).
No printer or PSUS4 settings were altered, printer driver in CUPS remains
the same.

I still do not understand why IPP hangs, you said Windows clients do not
implement IPP/1.1, but the fact remains Windows clients can print normally
under IPP protocol, and CUPS cannot.
Also, I have noticed while watching CUPS through it's web interface, that
CUPS first tries to use IPP/1.1, which fails, then falls back to IPP/1.0,
and then the job starts printing, but never finishes.

Current setup; Windows client still uses IPP, CUPS now uses LPD.

Some googling revealed that the device URI can end in several (some
undocumented?) ways, namely L1, P1, queue, or be accessed directly via
JetDirect on port 9100.
Manual as delivered with device speaks of IPP (Well, mine does).

Also, it appears the current device version is '1.00', and the stock
firmware (as delivered within the device) is '6350', yet the Linksys
website reports the latest firmware version as '6034' dated 2/01/2005.

Quirky setup, but at least it works now.