Well, I broke my printing somehow. Here is a relative slice from the cups error_log D [11/Feb/2004:20:51:46 +0800] [Job 236] Starting renderer D [11/Feb/2004:20:51:46 +0800] [Job 236] JCL: <job data> D [11/Feb/2004:20:51:46 +0800] [Job 236] D [11/Feb/2004:20:51:46 +0800] [Job 236] renderer PID kid4=10345 D [11/Feb/2004:20:51:46 +0800] [Job 236] renderer command: gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=bjc600 -dBitsPerPixel=1 -dProcessColorModel=/DeviceCMYK -sOutputFile=- - D [11/Feb/2004:20:51:46 +0800] [Job 236] foomatic-gswrapper: gs '-dBATCH' '-dPARANOIDSAFER' '-dQUIET' '-dNOPAUSE' '-sDEVICE=bjc600' '-dBitsPerPixel=1' '-dProcessColorModel=/DeviceCMYK' '-sOutputFile=| cat
&3' '/dev/fd/0' 3>&1 1>&2 D [11/Feb/2004:20:51:47 +0800] [Job 236] Unrecoverable error: rangecheck in .putdeviceprops D [11/Feb/2004:20:51:47 +0800] [Job 236] renderer return value: 255 D [11/Feb/2004:20:51:47 +0800] [Job 236] renderer received signal: 255 D [11/Feb/2004:20:51:47 +0800] [Job 236] Process dying with "The renderer command line returned an unrecognized error code 255.", exit stat: 1 D [11/Feb/2004:20:51:47 +0800] [Job 236] The renderer command line returned an unrecognized error code 255. D [11/Feb/2004:20:51:47 +0800] [Job 236] tail process done writing data to STDOUT D [11/Feb/2004:20:51:47 +0800] [Job 236] KID4 finished D [11/Feb/2004:20:51:47 +0800] [Job 236] D [11/Feb/2004:20:51:47 +0800] [Job 236] Closing renderer D [11/Feb/2004:20:51:47 +0800] [Job 236] KID3 exited with status 1 D [11/Feb/2004:20:51:47 +0800] [Job 236] Renderer exit stat: 1 D [11/Feb/2004:20:51:47 +0800] [Job 236] Renderer process finished D [11/Feb/2004:20:51:47 +0800] [Job 236] Killing process 10344 (KID3) D [11/Feb/2004:20:51:47 +0800] [Job 236] Process dying with "Error closing renderer", exit stat: 1 D [11/Feb/2004:20:51:47 +0800] [Job 236] Error closing renderer E [11/Feb/2004:20:51:47 +0800] PID 10341 stopped with status 1! D [11/Feb/2004:20:51:47 +0800] UpdateJob: job 236, file 0 is complete. D [11/Feb/2004:20:51:47 +0800] CancelJob: id = 236 D [11/Feb/2004:20:51:47 +0800] StopJob: id = 236, force = 0 D [11/Feb/2004:20:51:47 +0800] StopJob: printer state is 3
It appears to die in the process of processing the job to send it to the printer. I have been working (off and on) for 3 days on this and haven't figured it out. History: I have a heavily updated/modified 8.2. I am running 2.6.2 kernel, kde 3.2, cups 1.1.20. It has been working fine. Last week, I updated from 2.6.1 to 2.6.2, kde from 3.1.5 to 3.2, as well as a few other packages. I have checked and cannot see any suspect package. Every type of job I have tried fails (i.e. pdf from Acrobat, Mozilla printing through Kprinter and directly, command line, etc.). Besides checking through all the packages, I have built and upgraded the foomatic-filters package to the latest from linuxprinting.org, which changed the error message but still no go. I have tried booting back to 2.6.1, but printing still doesn't work, so I believe that clears the kernel (which is working really well BTW). I believe trying from the command line clears KDE 3.2, and IIANM, printing was still working after I upgraded to 3.2. The pertinent error log from the previous foomatic-rip was D [10/Feb/2004:09:40:45 +0800] [Job 217] Starting renderer D [10/Feb/2004:09:40:45 +0800] [Job 217] JCL: <job data> D [10/Feb/2004:09:40:45 +0800] [Job 217] D [10/Feb/2004:09:40:45 +0800] [Job 217] renderer PID pid4=7753 D [10/Feb/2004:09:40:45 +0800] [Job 217] renderer command: gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=bjc600 -dBitsPerPixel=1 -dProcessColorModel=/DeviceGray -sOutputFile=- - D [10/Feb/2004:09:40:46 +0800] [Job 217] foomatic-gswrapper: gs '-dBATCH' '-dPARANOIDSAFER' '-dQUIET' '-dNOPAUSE' '-sDEVICE=bjc600' '-dBitsPerPixel=1' '-dProcessColorModel=/DeviceGray' '-sOutputFile=| cat
&3' '/dev/fd/0' 3>&1 1>&2 D [10/Feb/2004:09:40:48 +0800] [Job 217] Error: /invalidfont in findfont D [10/Feb/2004:09:40:48 +0800] [Job 217] Operand stack: D [10/Feb/2004:09:40:48 +0800] [Job 217] bigFont Helvetica-Bold Font Helvetica-Bold 439086 Helvetica-Bold --nostringval-- Courier (Courier) Courier D [10/Feb/2004:09:40:48 +0800] [Job 217] Execution stack: D [10/Feb/2004:09:40:48 +0800] [Job 217] %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1 3 %oparray_pop 1 3 %oparray_pop 1 3 %oparray_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- 2 3 %oparray_pop 3 3 %oparray_pop --nostringval-- --nostringval-- --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 6 4 %oparray_pop --nostringval-- --nostringval-- --nostringval-- --nostringval-- D [10/Feb/2004:09:40:48 +0800] [Job 217] Dictionary stack: D [10/Feb/2004:09:40:48 +0800] [Job 217] --dict:1059/1417(ro)(G)-- --dict:0/20(G)-- --dict:91/200(L)-- --dict:17/17(ro)(G)-- --dict:1059/1417(ro)(G)-- D [10/Feb/2004:09:40:48 +0800] [Job 217] Current allocation mode is local D [10/Feb/2004:09:40:48 +0800] [Job 217] Last OS error: 2 D [10/Feb/2004:09:40:48 +0800] [Job 217] ESP Ghostscript 7.05.6: Unrecoverable error, exit code 1 D [10/Feb/2004:09:40:48 +0800] [Job 217] renderer return value: 1 D [10/Feb/2004:09:40:48 +0800] [Job 217] renderer received signal: 1 D [10/Feb/2004:09:40:48 +0800] [Job 217] Process dieing with "Possible error on renderer command line or PostScript error. Check options.", exit stat: 3 D [10/Feb/2004:09:40:48 +0800] [Job 217] Possible error on renderer command line or PostScript error. Check options. D [10/Feb/2004:09:40:48 +0800] [Job 217] tail process done writing data to STDOUT D [10/Feb/2004:09:40:48 +0800] [Job 217] KID4 finished D [10/Feb/2004:09:40:48 +0800] [Job 217] Flushing FIFO. D [10/Feb/2004:09:40:48 +0800] [Job 217] D [10/Feb/2004:09:40:48 +0800] [Job 217] Closing renderer D [10/Feb/2004:09:40:48 +0800] [Job 217] KID3 exited with status 3 D [10/Feb/2004:09:40:48 +0800] [Job 217] Renderer exit stat: 3 D [10/Feb/2004:09:40:48 +0800] [Job 217] Renderer process finished D [10/Feb/2004:09:40:48 +0800] [Job 217] Process dieing with "Error closing renderer", exit stat: 3 D [10/Feb/2004:09:40:48 +0800] [Job 217] Error closing renderer E [10/Feb/2004:09:40:48 +0800] PID 7749 stopped with status 3!
I have (because of the error message above) ran fonts-config -f but still no change. Any ideas where to start to look. TIA for any help, advice, etc. This one has me stumped. :-( -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
Hello, On Feb 11 22:20 Joe Morris (NTM) wrote (shortened):
D ... renderer command: gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=bjc600 -dBitsPerPixel=1 -dProcessColorModel=/DeviceCMYK -sOutputFile=- - ... D ... Unrecoverable error: rangecheck in .putdeviceprops
This is a Ghostscript error. Try whether or not the above renderer command works in a pipe on the command line with a clean PostScript input as follows: cat /usr/share/doc/packages/ghostscript/examples/colorcir.ps \ | gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE \ -sDEVICE=bjc600 -dBitsPerPixel=1 -dProcessColorModel=/DeviceCMYK \ -sOutputFile=- - \ | cat >/tmp/gs.out On my SUSE LINUX 9.0 system this command line works well. I didn't test it on a SuSE Linux 8.2 system. If the above command worked for you you can send the result to the printer with a command like cat /tmp/gs.out >/dev/lp0
... Every type of job I have tried fails (i.e. pdf from Acrobat, Mozilla printing through Kprinter and directly, command line, etc.).
This is strange because Ghostscript errors are usually caused by broken PostScript (or PDF) input.
D ... Error: /invalidfont in findfont D ... Operand stack: D ... bigFont Helvetica-Bold Font Helvetica-Bold 439086 Helvetica-Bold --nostringval-- Courier (Courier) Courier
Again a Ghostscript error. Here it fails to find fonts. For me it looks as if your Ghostscript stuff is broken. I may help to remove and re-install all Ghostscript packages: ghostscript-library ghostscript-x11 ghostscript-fonts-std ghostscript-fonts-other Kind regards Johannes Meixner -- SUSE LINUX AG, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
The Wednesday 2004-02-11 at 16:02 +0100, Johannes Meixner wrote:
This is a Ghostscript error. Try whether or not the above renderer command works in a pipe on the command line with a clean PostScript input as follows:
cat /usr/share/doc/packages/ghostscript/examples/colorcir.ps \ | gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE \ -sDEVICE=bjc600 -dBitsPerPixel=1 -dProcessColorModel=/DeviceCMYK \ -sOutputFile=- - \ | cat >/tmp/gs.out
On my SUSE LINUX 9.0 system this command line works well. I didn't test it on a SuSE Linux 8.2 system.
It does not work on my 8.2 with default SuSE patches (meaning: from you): cer@nimrodel:~> cat /tmp/gs.out Unrecoverable error: rangecheck in .putdeviceprops My printer is a canon 4000, and it uses the bjc600 device, I think.
For me it looks as if your Ghostscript stuff is broken.
Maybe not. My printer works correctly, but that pipe fails. The only problem I have is that photographs print horrible (since 8.1 installed cups), I have to go to windows to print them; this is a different problem altogether. (Horrible means very distorted colour, contrast, and density; If you know somebody to whom this can be reported, I'll do so, with scanned pages for verfication). -- Cheers, Carlos
Hello, On Feb 11 19:42 Carlos E. R. wrote (shortened):
My printer is a canon 4000, and it uses the bjc600 device, I think.
According to the rendering command it uses the bjc600 device.
The only problem I have is that photographs print horrible ... ... (Horrible means very distorted colour, contrast, and density ...
You should try out this PPD file: /usr/share/cups/model/Canon/BJC-4000-gimp-print.ppd.gz ("Canon BJC-4000 Foomatic/gimp-print") i.e. the Gimp-Print driver. On http://www.linuxprinting.org/show_printer.cgi?recnum=Canon-BJC-4000 the recommended driver is "bjc600" therefore this driver is used by default. By using the Gimp-Print driver you can adjust colours, contrast, brightness, saturation, gamma, and density. On http://gimp-print.sourceforge.net/p_Supported_Printers.php3 the Canon BJC 4000 is shown to work like the "bjc-4300" model of the Gimp-Print driver. The BJC 4300 is shown as "Operational" (not as "Fully Operational"). This means that you may have to do some testing and adjustments of the the driver settings go get this printer to work o.k. Regards Johannes Meixner -- SUSE LINUX AG, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
The Thursday 2004-02-12 at 09:39 +0100, Johannes Meixner wrote:
The only problem I have is that photographs print horrible ... ... (Horrible means very distorted colour, contrast, and density ...
You should try out this PPD file: /usr/share/cups/model/Canon/BJC-4000-gimp-print.ppd.gz ("Canon BJC-4000 Foomatic/gimp-print") i.e. the Gimp-Print driver.
I'm using two drivers. One is "Canon BJC-4000, Foomatic , gimp-print (en)" (with «PCFileName: "GIMP-PRI.PPD"») and the other on is "Canon BJC-4000, Foomatic + bjc600 (recommended)" (with «PCFileName: "BJC600.PPD"»). I also tried "CANON BJC 4300, CUPS+Gimp-Print v4.2.5". The gimp driver prints quite slowly, with reasonable quality - but the result has noticeable worse quality than what I get in windows. The other driver (bjc600) is quite fast, produces good quality text, but photographs are simply horrible. They get very strange colours; I can not easily explain: not exactly low quality, they are heavily distorted. It's similar to using gimp, posterize to 6 levels: that's the best comparison I can give. I can not understand it, but this has been consistent both in SuSE 8.1 and 8.2. And strangely, if I print as grays, the result is similar. Horrible. I can scan a sample printed on a page and mail it to you, or to feedback, and you can better judge for yourself.
On http://www.linuxprinting.org/show_printer.cgi?recnum=Canon-BJC-4000 the recommended driver is "bjc600" therefore this driver is used by default.
But that is the one that prints bad photographs. I don't know if it works for them, but it doesn't for me.
By using the Gimp-Print driver you can adjust colours, contrast, brightness, saturation, gamma, and density.
Yes, I know. That's the one I use when I have to print pages with text and photographs. Unfortunately, when I need better quality, I have to print to postscript, convert to pdf, switch to windows, print to file, back to Linux, and print the file using the raw queue.
On http://gimp-print.sourceforge.net/p_Supported_Printers.php3 the Canon BJC 4000 is shown to work like the "bjc-4300" model of the Gimp-Print driver. The BJC 4300 is shown as "Operational" (not as "Fully Operational"). This means that you may have to do some testing and adjustments of the the driver settings go get this printer to work o.k.
The 4300 model also has a photograph quality mode, when using a special cartridge: I'd guess that's the part that is not complete. The rest should be equivalent to the BJC-4000, which is a 1995 printer. With the bjc600 I tried everything I could think off, but result is no good - except the demo pages from cups, that prints correctly. -- Cheers, Carlos Robinson
On 02/11/2004 11:02 PM, Johannes Meixner wrote:
D ... Unrecoverable error: rangecheck in .putdeviceprops
This is a Ghostscript error. Try whether or not the above renderer command works in a pipe on the command line with a clean PostScript input as follows:
cat /usr/share/doc/packages/ghostscript/examples/colorcir.ps \ | gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE \ -sDEVICE=bjc600 -dBitsPerPixel=1 -dProcessColorModel=/DeviceCMYK \ -sOutputFile=- - \ | cat >/tmp/gs.out
If the above command worked for you you can send the result to the printer with a command like cat /tmp/gs.out >/dev/lp0
This did not work either. But it helped.
... Every type of job I have tried fails (i.e. pdf from Acrobat, Mozilla printing through Kprinter and directly, command line, etc.).
This is strange because Ghostscript errors are usually caused by broken PostScript (or PDF) input.
Well, this was a strange problem. I am pretty sure I got it though.
D ... Error: /invalidfont in findfont D ... Operand stack: D ... bigFont Helvetica-Bold Font Helvetica-Bold 439086 Helvetica-Bold --nostringval-- Courier (Courier) Courier
Again a Ghostscript error. Here it fails to find fonts.
For me it looks as if your Ghostscript stuff is broken. I may help to remove and re-install all Ghostscript packages: ghostscript-library ghostscript-x11 ghostscript-fonts-std ghostscript-fonts-other
I tried reinstalling the above, but no change. I started checking which packages had been installed since I was last able to print. Turns out kde 3.2 was installed after I last successfully printed. Tried a different user- printing worked. Tried mv .kde.kde to start with fresh kde settings (but not seeing how the other printing methods could be affected), but it did not change. I compared my home directory to other users on the machine. I cleaned out temp, still wouldn't print. I noticed 2 files in mine (that might be related) not in the others, .kderc and .lpoptions. I renamed .kderc and deleted .lpoptions. I suspect the .lpoptions file was it, but at least now after how many hours of searching and testing, I can print as my normal user again. I don't know how I got the file, or why or what it did, but I am happy. Thanks very much for your help Johannes for helping me through the "I think I tried everything and have run out of ideas" stage. Much appreciated. Now, to get to printing.... -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
Hello, On Feb 12 19:14 Joe Morris (NTM) wrote (shortened):
... Turns out kde 3.2 was installed after I last successfully printed. ... I renamed .kderc and deleted .lpoptions. ... now ... I can print
Regarding ~/.lpoptions (and /etc/cups/lpoptions) see http://portal.suse.com/sdb/en/2002/11/jsmeix_print-cups-options.html Regarding KDE specific files see for example http://portal.suse.com/sdb/en/2002/10/mmichna_cups_margins.html (it may change from KDE version to KDE version which files and which information is stored in the user's home directory) Regards Johannes Meixner -- SUSE LINUX AG, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
On 02/12/2004 08:35 PM, Johannes Meixner wrote:
Regarding ~/.lpoptions (and /etc/cups/lpoptions) see http://portal.suse.com/sdb/en/2002/11/jsmeix_print-cups-options.html
Regarding KDE specific files see for example http://portal.suse.com/sdb/en/2002/10/mmichna_cups_margins.html (it may change from KDE version to KDE version which files and which information is stored in the user's home directory)
Excellent references! Now I know where it came from and why it probably caused the failure. Thanks much for passing on your knowledge to us all. I really appreciate it! ;-) -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
participants (3)
-
Carlos E. R.
-
Joe Morris (NTM)
-
Johannes Meixner