Corvash
2005-02-02, 07:49 AM CST
I'm trying to print to a printer over the network (HP Officejet G95, it's attached directly onto the network).
The print job will enter the queue, and either completes unusually fast (if added using lpd on the command line) or just sits there in the queue (if added via cups), if I set the loglevel to debug I find the following in /var/log/cups/error_log. Nothing is actually printed.
D [03/Feb/2005:00:05:31 +0930] [Job 1] Closing renderer
D [03/Feb/2005:00:05:31 +0930] [Job 1] KID3 exited with status 3
D [03/Feb/2005:00:05:31 +0930] [Job 1] Renderer exit stat: 3
D [03/Feb/2005:00:05:31 +0930] [Job 1] Renderer process finished
D [03/Feb/2005:00:05:31 +0930] [Job 1] Killing process 3887 (KID3)
D [03/Feb/2005:00:05:31 +0930] [Job 1] Process dying with "Error closing renderer", exit stat: 3
D [03/Feb/2005:00:05:31 +0930] [Job 1] Error closing renderer
E [03/Feb/2005:00:05:31 +0930] PID 3884 stopped with status 3!
Fiddling with choice of print driver produced only one printout (using PCL3), which had the positioning and dimensions of objects mangled (and most objects doubled). Additional attempts failed to replicate this, and it appears to be an unusual fluke.
The print job will enter the queue, and either completes unusually fast (if added using lpd on the command line) or just sits there in the queue (if added via cups), if I set the loglevel to debug I find the following in /var/log/cups/error_log. Nothing is actually printed.
D [03/Feb/2005:00:05:31 +0930] [Job 1] Closing renderer
D [03/Feb/2005:00:05:31 +0930] [Job 1] KID3 exited with status 3
D [03/Feb/2005:00:05:31 +0930] [Job 1] Renderer exit stat: 3
D [03/Feb/2005:00:05:31 +0930] [Job 1] Renderer process finished
D [03/Feb/2005:00:05:31 +0930] [Job 1] Killing process 3887 (KID3)
D [03/Feb/2005:00:05:31 +0930] [Job 1] Process dying with "Error closing renderer", exit stat: 3
D [03/Feb/2005:00:05:31 +0930] [Job 1] Error closing renderer
E [03/Feb/2005:00:05:31 +0930] PID 3884 stopped with status 3!
Fiddling with choice of print driver produced only one printout (using PCL3), which had the positioning and dimensions of objects mangled (and most objects doubled). Additional attempts failed to replicate this, and it appears to be an unusual fluke.