[cups] Print Queue out of order
Helge Blischke
helgeblischke at web.de
Wed Feb 17 01:38:53 PST 2016
> Am 17.02.2016 um 09:30 schrieb Meyer Klaus <kmeyer at dohle.com>:
>
>
Look at these lines of the error_log:
D [26/Jan/2016:11:45:02 +0100] [Job 5375616] Process is dying with "Caught termination signal: Job canceled
D [26/Jan/2016:11:45:02 +0100] [Job 5375616] ", exit stat 0
D [26/Jan/2016:11:45:02 +0100] [Job 5375616] Cleaning up...
D [26/Jan/2016:11:45:02 +0100] [Job 5375616] Process is dying with "Caught termination signal: Job canceled
D [26/Jan/2016:11:45:02 +0100] [Job 5375616] ", exit stat 0
D [26/Jan/2016:11:45:02 +0100] [Job 5375616] Cleaning up...
D [26/Jan/2016:11:45:02 +0100] [Job 5375616] Killing kid4
D [26/Jan/2016:11:45:02 +0100] [Job 5375616] Process is dying with "Caught termination signal: Job canceled
D [26/Jan/2016:11:45:02 +0100] [Job 5375616] ", exit stat 0
D [26/Jan/2016:11:45:02 +0100] [Job 5375616] Cleaning up...
D [26/Jan/2016:11:45:02 +0100] [Job 5375616] Killing pdf-to-ps
D [26/Jan/2016:11:45:09 +0100] [CGI] cgiSetArray: job_id[0]="5375616"
D [26/Jan/2016:11:45:10 +0100] [Job 5375616] Killing kid3
Obviously the foomatic-rip filter cancels the job in response to the queue being stopped
(I have no idea why you need to restart cups to get the queue working again).
I think you need to file a bug for the cups-filters package from open printing.org
(or revert to the PostScript centric workflow you had with the 1.3.9 version of cups).
Helge
More information about the cups
mailing list