Ipp printing job never completes though prints fine (Dapper)

[Andrew Waldram]

when I send a print job to my epson r300 via ipp (it's on a 2003 Domain Controller)
the job gets submitted the my ubuntu client states the printer is halted.

If I resume the printer then the same job prints again.

deleteing the job then resuming works round this.

in the log I get
E [27/Nov/2005:18:29:38 +0000] cupsdAuthorize: Local authentication certificate not
found!
E [27/Nov/2005:18:29:43 +0000] cupsdAuthorize: Local authentication certificate not
found!
E [27/Nov/2005:18:29:43 +0000] cupsdAuthorize: Local authentication certificate not
found!
E [27/Nov/2005:18:29:43 +0000] cupsdAuthorize: Local authentication certificate not
found!
I [27/Nov/2005:18:30:03 +0000] Started "/usr/lib/cups/daemon/cups-driverd" (pid=5749)
E [27/Nov/2005:18:30:06 +0000] [cups-driverd] Unable to open driver
directory "/usr/lib/cups/driver": No such file or directory
I [27/Nov/2005:18:30:07 +0000] Started "/usr/lib/cups/daemon/cups-deviced" (pid=5751)
I [27/Nov/2005:18:30:11 +0000] Adding start banner page "none" to job 39.
I [27/Nov/2005:18:30:11 +0000] Adding end banner page "none" to job 39.
I [27/Nov/2005:18:30:11 +0000] Job 39 queued on 'Stylus-Photo-R300' by 'andy'.
I [27/Nov/2005:18:30:11 +0000] Started filter /usr/lib/cups/filter/pstops (PID 580
for job 39.
I [27/Nov/2005:18:30:11 +0000] Started filter /usr/lib/cups/filter/pstoraster (PID
5809) for job 39.
I [27/Nov/2005:18:30:11 +0000] Started filter /usr/lib/cups/filter/rastertoprinter
(PID 5811) for job 39.
I [27/Nov/2005:18:30:11 +0000] Started backend /usr/lib/cups/backend/http (PID 5812)
for job 39.
N [27/Nov/2005:18:30:31 +0000] [Job 39] Print file accepted - job ID 19.
E [27/Nov/2005:18:31:02 +0000] [Job 39] Unable to get job 19 attributes (client-error-
not-possible)!
E [27/Nov/2005:18:31:02 +0000] PID 5812 stopped with status 1!
I [27/Nov/2005:18:31:02 +0000] Hint: Try setting the LogLevel to "debug" to find out
more.
I [27/Nov/2005:18:31:02 +0000] Saving printers.conf...

As you can see the job was submitted fine

this only seems to affect ipp as my lj5 conects via smb on a debian linux server is
fine.

if i enable debug then no errors appear in the log !!!

I suspect the 'client-error-not-possible' is probably correct (gotta love mickysoft)
but surely the job has printed so should finnish with error 0.

the Problem appears to be in the http backend.

[Andrew Waldram (andrew-waldram)]

according to RFC 2639
client-error-not-possible: The request cannot be carried out
         because of the state of the system. See also 'server-error-
         not-accepting-jobs' status code which MUST take precedence if
         the Printer object's "printer-accepting-jobs" attribute is '
         false'.

so the client is stating the server is not accepting jobs but just before we have
Print file accepted - job ID 19.

So this looks like a serious bug in the cups implenetenation (it did not happen
in Breezy so is a regression).

Is anyone out there looking at the cups system?? I see multiple recompiles but
no improvement or acknowledgement of this broken functiality.

[Andrew Waldram (andrew-waldram)]

hers a work around not sure why it works though
log on the cups admin
http://localhost:631/admin/?op=config-printer&printer_name=Stylus-Photo-R300
change the error policy to
Stylus-Photo-R300: Policies
 Error Policy: ABORT-JOB
 Operation Policy:
click continue you get

Error:

    server-error-internal-error

and if you check printers.conf it still is set as

<Printer Stylus-Photo-R300>
Info Stylus-Photo-R300
DeviceURI http://tub/printers/r300/.printer
State Idle
Accepting Yes
Shared Yes
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
ErrorPolicy stop-printer
</Printer>

yet now the submitted job now prints clears and leaves the printer ready

[Martin Pitt (pitti)]

Do you still have this problem with the current dapper version? (1.2rc2)

[Andrew Waldram (andrew-waldram)]

No cleared with neglect ;-)

I'd close it if I knew how

[Manuel López-Ibáñez (manuellopezibanez)]

Hi Matthias, do you think we can close this? It seems it has been fixed by one of the latest cups 1.2.0 releases.

[Hendy Irawan (ceefour)]

See also:

http://www.hendyirawan.com/2008/01/30/how-to-print-or-make-pdf-files-in-ubuntulinux/

Who knows it can fix your problem.