Tim Waugh wrote:
> The network print server is using an implementation of IPP. When CUPS
> has sent the job to it using the IPP backend, the backend waits until
> the job has finished. It does this by repeatedly sending the
> Get-Job-Attributes IPP request.
>
> The print server is responding with success, but either has no
> 'job-state' attribute included in the reply or else the job-state is
> IPP_JOB_PENDING, IPP_JOB_HELD, IPP_JOB_PROCESSING or IPP_JOB_STOPPED.
>
> Try running the following command, replacing 'theprintserver' with the
> hostname of the print server:
>
> python <<EOF
> import cups, pprint
> cups.setServer("theprintserver")
> c=cups.Connection()
> pprint.pprint(c.getJobs())
> EOF
Ok... here's what happens:
[root@lancre ~]# python <<EOF
> import cups, pprint
> cups.setServer("ep0")
> c=cups.Connection()
> pprint.pprint(c.getJobs())
> EOF
Traceback (most recent call last):
File "<stdin>", line 4, in <module>
cups.IPPError: (1030, 'client-error-not-found')
--
-John (john@xxxxxxxxxxx)
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
