Unrecoverable error rangecheck in putdeviceprops

Pages: 1
  • Index
  • » Applications & Desktop Environments
  • » ImageMagick fails to convert a PDF file (GhostScript can’t find file?)

Pages: 1

#1 2012-01-29 00:59:51

Stalafin
Member
From: Berlin, Germany
Registered: 2007-10-26
Posts: 617

ImageMagick fails to convert a PDF file (GhostScript can’t find file?)

I was trying to convert a .pdf file into a .png file with imagemagick (here is the sample pdf file: http://ompldr.org/vY2ljcg ).

However, apparently ImageMagick already failed simply opening the file:

$ convert main.pdf main.png
Unrecoverable error: rangecheck in .putdeviceprops
sfopen: gs_parse_file_name failed.
  ./base/gsicc_manage.c:866: gsicc_open_search(): Could not find lab.icc 
| ./psi/zusparam.c:856: set_lab_icc(): cannot find default lab icc profile
convert: Postscript delegate failed `main.pdf': No such file or directory @ error/pdf.c/ReadPDFImage/665.
convert: missing an image filename `main.png' @ error/convert.c/ConvertImageCommand/3016.

Any ideas?

#2 2012-01-29 07:01:36

redguardtoo
Member
From: China, Shanghai
Registered: 2007-11-28
Posts: 43
Website

Re: ImageMagick fails to convert a PDF file (GhostScript can’t find file?)

try pdftoppm in poppler. then convert the ppm to png.

ImageMagic use ghostscript, ghostscript is not as error tolerant as poppler.

Last edited by redguardtoo (2012-01-29 07:02:13)


Help me, Help you
Intel(R) Core(TM) i3 + 3G + GeForce GST 250
Archlinux+musca+tint2+netcfg

#3 2012-01-29 19:47:55

Stalafin
Member
From: Berlin, Germany
Registered: 2007-10-26
Posts: 617

Re: ImageMagick fails to convert a PDF file (GhostScript can’t find file?)

Thanks, that of course is one solution. I could also just use pdfdraw from mupdf, which would work.

I am quite surprised still that ghostscript seems to have some problems there, which is a shame, because ImageMagick’s other functions are quite useful.

I am not tagging this [solved] quite yet, because in fact the problem still persists. Maybe somebody else has an idea.

#4 2012-01-30 05:44:28

redguardtoo
Member
From: China, Shanghai
Registered: 2007-11-28
Posts: 43
Website

Re: ImageMagick fails to convert a PDF file (GhostScript can’t find file?)

put it this way. if all PDF creator produces only standard PDF, then ghostscript is fine. But most PDF creator don’t (except Adobe Acrobat). So a compatible pdf reader need handle non-standard PDFs. It’s a long-term boring maintaining job which need much human resource.

My impression is poppler’s community is the most active one which means it has more volunteers to fix bugs.

I am familiar with all the open sourced PDF engines because I did PDF application for 3 years.

Last edited by redguardtoo (2012-01-30 06:04:58)


Help me, Help you
Intel(R) Core(TM) i3 + 3G + GeForce GST 250
Archlinux+musca+tint2+netcfg

#5 2012-02-27 03:57:15

lajos
Member
Registered: 2010-08-12
Posts: 5

Re: ImageMagick fails to convert a PDF file (GhostScript can’t find file?)

redguardtoo wrote:

poppler’s community is the most active one which means it has more volunteers to fix bugs

Thanks so much for the poppler suggestion! It works perfectly. I had the same issue with imagemagick as OP.

pdftoppm can even output png files with the -png option (other formats are also supported, look an the man page).

#6 2014-08-30 23:00:46

hepha
Member
Registered: 2012-07-20
Posts: 13

Re: ImageMagick fails to convert a PDF file (GhostScript can’t find file?)

I have this error installed ghostscript-git to normal for your reference

sfopen: gs_parse_file_name failed.
  ./base/gsicc_manage.c:1050: gsicc_open_search(): Could not find `
| ./base/gsicc_manage.c:1651: gsicc_set_device_profile(): cannot find device profile

I recently setup a new Macbook with 10.9.4 installed. But since that, I cannot use an script to convert PDF files to PNG anymore. It seems like my ImageMagick installation cannot find Ghostscript. I tried to install both several times(using .pkg installers), but nothing changed anything.

Here is my convert command:

convert -density 144x144 -quality 90 file.pdf file.png

And all I am getting is this:

Unrecoverable error: rangecheck in .putdeviceprops
sfopen: gs_parse_file_name failed.
./base/gsicc_manage.c:866: gsicc_open_search(): Could not find lab.icc
| ./psi/zusparam.c:856: set_lab_icc(): cannot find default lab icc profile
convert: Postscript delegate failed 'file.pdf': No such file or directory @ error/pdf.c/ReadPDFImage/665.
convert: missing an image filename 'file.png' @ error/convert.c/ConvertImageCommand/3016.

It kinda says that it has problems with my pdf delegates. So, when I look at the delegates of my ImageMagick installation, it says so as well(convert -list configure):

Path: /opt/local/lib/ImageMagick-6.7.4/config/configure.xml
Name Value
-------------------------------------------------------------------------------
CC            /Developer/usr/bin/clang
CFLAGS        -pipe -O2 -arch x86_64 -Wall -D_THREAD_SAFE -pthread
CODER_PATH    /opt/local/lib/ImageMagick-6.7.4/modules-Q16/coders
CONFIGURE     ./configure  '--prefix=/opt/local' '--enable-shared' '--enable-static' '--disable-    ltdl-install' '--with-frozenpaths' '--without-openexr' '--disable-hdri' '--with-dps' '--with-bzlib' '--with-fontconfig' '--with-gslib' '--with-jpeg' '--with-lcms' '--with-png' '--with-tiff' '--with-zlib' '--with-modules' '--with-xml' '--with-x' '--without-perl' '--without-fpx' '--without-jbig' '--without-jp2' '--without-wmf' '--without-gvc' '--without-rsvg' '--without-lqr' '--with-gs-font-dir=/opt/local/share/fonts/urw-fonts' '--with-quantum-depth=16' 'CC=/Developer/usr/bin/clang' 'CFLAGS=-pipe -O2 -arch x86_64' 'LDFLAGS=-L/opt/local/lib -arch x86_64' 'CPPFLAGS=-I/opt/local/include' 'CXX=/Developer/usr/bin/clang++' 'CXXFLAGS=-pipe -O2 -arch x86_64'
CONFIGURE_PATH /opt/local/etc/ImageMagick/
COPYRIGHT     Copyright (C) 1999-2011 ImageMagick Studio LLC
CPPFLAGS      -I/opt/local/include/ImageMagick
CXX           /Developer/usr/bin/clang++
CXXFLAGS      -pipe -O2 -arch x86_64 -D_THREAD_SAFE -pthread
DEFS          -DHAVE_CONFIG_H
DELEGATES     bzlib fontconfig freetype gs jpeg jng lcms2 lzma png tiff x11 xml zlib
DISTCHECK_CONFIG_FLAGS 'CC=/Developer/usr/bin/clang' 'CFLAGS=-pipe -O2 -arch x86_64' 'CPPFLAGS=-I/opt/local/include' 'CXX=/Developer/usr/bin/clang++' 'LDFLAGS=-L/opt/local/lib -arch x86_64' --disable-deprecated --with-quantum-depth=16 --with-umem=no --with-autotrace=no --with-fpx=no --with-fontpath= --with-gs-font-dir=/opt/local/share/fonts/urw-fonts --with-gvc=no --with-jp2=no --with-lqr=no --with-openexr=no --with-rsvg=no --with-wmf=no --with-perl=no
DOCUMENTATION_PATH /opt/local/share/doc/ImageMagick/
EXEC-PREFIX   /opt/local
EXECUTABLE_PATH /opt/local/bin
FEATURES      
FILTER_PATH   /opt/local/lib/ImageMagick-6.7.4/modules-Q16/filters
HOST          x86_64-apple-darwin11.2.0
INCLUDE_PATH  /opt/local/include/ImageMagick
LDFLAGS       -L/opt/local/lib -L/opt/local/lib -arch x86_64 -L/opt/local/lib -L/opt/local/lib
LIB_VERSION   0x674
LIB_VERSION_NUMBER 6,7,4,0
LIBRARY_PATH  /opt/local/lib/ImageMagick-6.7.4
LIBS          -lMagickCore -llcms2 -ltiff -lfreetype -ljpeg -L/opt/local/lib -lfontconfig -lXext -lSM -lICE -lX11 -lXt -L/opt/local/lib -llzma -lbz2 -lz -lm -lgomp -lpthread -lltdl
NAME          ImageMagick
PCFLAGS       
PREFIX        /opt/local
QuantumDepth  16
RELEASE_DATE  2012-01-09
SHARE_PATH    /opt/local/share/ImageMagick-6.7.4
SVN_REVISION  6163
TARGET_CPU    x86_64
TARGET_OS     darwin11.2.0
TARGET_VENDOR apple
VERSION       6.7.4
WEBSITE       http://www.imagemagick.org

Path: [built-in]

Name          Value`
-------------------------------------------------------------------------------
NAME          ImageMagick

So, I guess the delegate line is the interesting one:

bzlib fontconfig freetype gs jpeg jng lcms2 lzma png tiff x11 xml zlib

No PDF there, but how can I add it? In case you think I don’t have ghostscript installed(as many hints via google suggested), here is my ghostscript installation:

GPL Ghostscript 9.04 (2011-08-05)
Copyright (C) 2011 Artifex Software, Inc. All rights reserved.

So, what is wrong here? Is «just» the PDF delegate missing? But how do I add it then? Is GS maybe configured wrong? What can I do to fix it? Any suggestion would be highly appreciated — I am completely out of ideas!

Many thanks in advance!


Description


Dave Smith



2011-12-20 18:03:04 UTC

I am running this command on Fedora 15 x64. It works fine under ghostscript 8.x. It is simulating a call I am running using the ghostscript API.


 gs -dQUIET -dNOPAUSE -dBATCH -dSAFER -sDEVICE=display -dDisplayHandle=0 -dDisplayFormat=2052 -dDisplayResolution=300  -f /tmp/sample.pdf 


Unrecoverable error: typecheck in .putdeviceprops
sfopen: gs_parse_file_name failed.
  ./base/gsicc_manage.c:866: gsicc_open_search(): Could not find lab.icc 
| ./psi/zusparam.c:871: set_lab_icc(): cannot find default lab icc profile

 gs --help
GPL Ghostscript 9.04 (2011-08-05)
Search path:
   /usr/share/ghostscript/9.04/Resource/Init :
   /usr/share/ghostscript/9.04/lib :
   /usr/share/ghostscript/9.04/Resource/Font :
   /usr/share/ghostscript/fonts : /usr/share/fonts/default/ghostscript :
   /usr/share/fonts/default/Type1 : /usr/share/fonts/default/amspsfnt/pfb :
   /usr/share/fonts/default/cmpsfont/pfb : /usr/share/fonts :
   /usr/share/ghostscript/conf.d : /etc/ghostscript :
   /etc/ghostscript/9.04 : /usr/share/poppler/cMap/Adobe-CNS1 :
   /usr/share/poppler/cMap/Adobe-GB1 :
   /usr/share/poppler/cMap/Adobe-Japan1 :
   /usr/share/poppler/cMap/Adobe-Japan2 :
   /usr/share/poppler/cMap/Adobe-Korea1

 ls /usr/share/ghostscript/9.04/iccprofiles
default_cmyk.icc  default_gray.icc  default_rgb.icc  gray_to_k.icc  lab.icc  ps_cmyk.icc  ps_gray.icc  ps_rgb.icc  sgray.icc  srgb.icc


Comment 3


Chris Liddell (chrisl)



2011-12-20 18:19:39 UTC

Well, in that case, you'll really have to provide us with a sample file to test.


Comment 5


Chris Liddell (chrisl)



2011-12-20 18:34:55 UTC

Well, it *seems* to work fine with the current master in our git repository, and with the (patched) 9.04 release in the Ubuntu Oneiric 11.10 release, so it's probably a issue that's been fixed since 9.04 was released.


Comment 6


Dave Smith



2011-12-20 19:00:13 UTC

(In reply to comment #5)
> Well, it *seems* to work fine with the current master in our git repository,
> and with the (patched) 9.04 release in the Ubuntu Oneiric 11.10 release, so
> it's probably a issue that's been fixed since 9.04 was released.

OK. I downloaded the Fedora 16 rpm and it is not fixed in there. Should I take this up with Fedora ? Or is there a patch I can apply...


Comment 7


Chris Liddell (chrisl)



2011-12-20 19:56:00 UTC

Well, I think that patch I indicated above was the only fix in this area that was in the Postscript resources, so anything else will mean patching the Ghostcript source, and rebuilding the binary.

Given that, you'll probably need to go through the package maintainer anyway.


Also, I can't find a list of patches Ubuntu has adopted since our 9.04 release.


Comment 8


Dave Smith



2011-12-20 20:16:42 UTC

(In reply to comment #7)
> Well, I think that patch I indicated above was the only fix in this area that
> was in the Postscript resources, so anything else will mean patching the
> Ghostcript source, and rebuilding the binary.
> 
> Given that, you'll probably need to go through the package maintainer anyway.
> 
> 
> Also, I can't find a list of patches Ubuntu has adopted since our 9.04 release.

Opened a ticket at Fedora 


https://bugzilla.redhat.com/show_bug.cgi?id=769436


Comment 9


Dave Smith



2011-12-21 20:59:58 UTC

(In reply to comment #8)
> (In reply to comment #7)
> > Well, I think that patch I indicated above was the only fix in this area that
> > was in the Postscript resources, so anything else will mean patching the
> > Ghostcript source, and rebuilding the binary.
> > 
> > Given that, you'll probably need to go through the package maintainer anyway.
> > 
> > 
> > Also, I can't find a list of patches Ubuntu has adopted since our 9.04 release.
> 
> Opened a ticket at Fedora 
> 
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=769436


Did you try this on 64 bit or 32 bit? I found this that seems to describe the same problem ...

http://www.ghostscript.com/pipermail/gs-devel/2010-July/008785.html


Comment 10


Dave Smith



2011-12-21 21:01:18 UTC

(In reply to comment #8)
> (In reply to comment #7)
> > Well, I think that patch I indicated above was the only fix in this area that
> > was in the Postscript resources, so anything else will mean patching the
> > Ghostcript source, and rebuilding the binary.
> > 
> > Given that, you'll probably need to go through the package maintainer anyway.
> > 
> > 
> > Also, I can't find a list of patches Ubuntu has adopted since our 9.04 release.
> 
> Opened a ticket at Fedora 
> 
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=769436


Did you try this on 64 bit or 32 bit? I found this that seems to describe the same problem ...

http://www.ghostscript.com/pipermail/gs-devel/2010-July/008785.html
(In reply to comment #9)
> (In reply to comment #8)
> > (In reply to comment #7)
> > > Well, I think that patch I indicated above was the only fix in this area that
> > > was in the Postscript resources, so anything else will mean patching the
> > > Ghostcript source, and rebuilding the binary.
> > > 
> > > Given that, you'll probably need to go through the package maintainer anyway.
> > > 
> > > 
> > > Also, I can't find a list of patches Ubuntu has adopted since our 9.04 release.
> > 
> > Opened a ticket at Fedora 
> > 
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id=769436
> 
> 
> Did you try this on 64 bit or 32 bit? I found this that seems to describe the
> same problem ...
> 
> http://www.ghostscript.com/pipermail/gs-devel/2010-July/008785.html

Sorry, I forgot to add I downloaded the source from the git repo and build it on Fedora 15 64 bit and got the same error.


Comment 11


Dave Smith



2011-12-21 22:07:05 UTC

(In reply to comment #8)
> (In reply to comment #7)
> > Well, I think that patch I indicated above was the only fix in this area that
> > was in the Postscript resources, so anything else will mean patching the
> > Ghostcript source, and rebuilding the binary.
> > 
> > Given that, you'll probably need to go through the package maintainer anyway.
> > 
> > 
> > Also, I can't find a list of patches Ubuntu has adopted since our 9.04 release.
> 
> Opened a ticket at Fedora 
> 
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=769436


Did you try this on 64 bit or 32 bit? I found this that seems to describe the same problem ...

http://www.ghostscript.com/pipermail/gs-devel/2010-July/008785.html
(In reply to comment #9)
> (In reply to comment #8)
> > (In reply to comment #7)
> > > Well, I think that patch I indicated above was the only fix in this area that
> > > was in the Postscript resources, so anything else will mean patching the
> > > Ghostcript source, and rebuilding the binary.
> > > 
> > > Given that, you'll probably need to go through the package maintainer anyway.
> > > 
> > > 
> > > Also, I can't find a list of patches Ubuntu has adopted since our 9.04 release.
> > 
> > Opened a ticket at Fedora 
> > 
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id=769436
> 
> 
> Did you try this on 64 bit or 32 bit? I found this that seems to describe the
> same problem ...
> 
> http://www.ghostscript.com/pipermail/gs-devel/2010-July/008785.html

Sorry, I forgot to add I downloaded the source from the git repo and build it on Fedora 15 64 bit and got the same error.
(In reply to comment #10)
> (In reply to comment #8)
> > (In reply to comment #7)
> > > Well, I think that patch I indicated above was the only fix in this area that
> > > was in the Postscript resources, so anything else will mean patching the
> > > Ghostcript source, and rebuilding the binary.
> > > 
> > > Given that, you'll probably need to go through the package maintainer anyway.
> > > 
> > > 
> > > Also, I can't find a list of patches Ubuntu has adopted since our 9.04 release.
> > 
> > Opened a ticket at Fedora 
> > 
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id=769436
> 
> 
> Did you try this on 64 bit or 32 bit? I found this that seems to describe the
> same problem ...
> 
> http://www.ghostscript.com/pipermail/gs-devel/2010-July/008785.html
> (In reply to comment #9)
> > (In reply to comment #8)
> > > (In reply to comment #7)
> > > > Well, I think that patch I indicated above was the only fix in this area that
> > > > was in the Postscript resources, so anything else will mean patching the
> > > > Ghostcript source, and rebuilding the binary.
> > > > 
> > > > Given that, you'll probably need to go through the package maintainer anyway.
> > > > 
> > > > 
> > > > Also, I can't find a list of patches Ubuntu has adopted since our 9.04 release.
> > > 
> > > Opened a ticket at Fedora 
> > > 
> > > 
> > > https://bugzilla.redhat.com/show_bug.cgi?id=769436
> > 
> > 
> > Did you try this on 64 bit or 32 bit? I found this that seems to describe the
> > same problem ...
> > 
> > http://www.ghostscript.com/pipermail/gs-devel/2010-July/008785.html
> 
> Sorry, I forgot to add I downloaded the source from the git repo and build it
> on Fedora 15 64 bit and got the same error.

I downloaded the source out of git and built on Fedora 15 and get the same error.

Did you try this on 64 bit or 32 bit? I found this that seems to describe the
same problem ...

http://www.ghostscript.com/pipermail/gs-devel/2010-July/008785.html


Comment 12


Chris Liddell (chrisl)



2011-12-21 22:16:03 UTC

I did, but with limited support for the display device, I only got it to run the file without the ICC profile error, I didn't try any further.

Now I have, and it seems there's a little "hiccup". I haven't a clue how this worked on 8.x, but......

It seems that, because one of the things DisplayHandle can be is a pointer value, and on 64 bit builds, that can (obviously!) be longer than 32 bits. But Postscript only allows 32 bit number values, and these settings work through the Postscript machinery, it needs to be compatible with that limitation.

So, on 64 bit systems the parameter for DisplayHandle is expected to be a string, rather than an integer or a long. So, if you convert your DisplayHandle parameter to a string, and use

-sDisplayHandle="handle value string"


That *might* help.


Comment 13


Dave Smith



2011-12-21 22:23:20 UTC

(In reply to comment #12)
> I did, but with limited support for the display device, I only got it to run
> the file without the ICC profile error, I didn't try any further.
> 
> Now I have, and it seems there's a little "hiccup". I haven't a clue how this
> worked on 8.x, but......
> 
> It seems that, because one of the things DisplayHandle can be is a pointer
> value, and on 64 bit builds, that can (obviously!) be longer than 32 bits. But
> Postscript only allows 32 bit number values, and these settings work through
> the Postscript machinery, it needs to be compatible with that limitation.
> 
> So, on 64 bit systems the parameter for DisplayHandle is expected to be a
> string, rather than an integer or a long. So, if you convert your DisplayHandle
> parameter to a string, and use
> 
> -sDisplayHandle="handle value string"
> 
> 
> That *might* help.

Did not work, tried -dDisplayHandle="0". The reason I brought this back up is that I installed 64 bit 8.71 and it failed with the same error. All my running installs are 32 bit, this is the first crack at 64 bit....


Comment 14


Chris Liddell (chrisl)



2011-12-21 22:25:15 UTC

(In reply to comment #13)
> (In reply to comment #12)
> > I did, but with limited support for the display device, I only got it to run
> > the file without the ICC profile error, I didn't try any further.
> > 
> > Now I have, and it seems there's a little "hiccup". I haven't a clue how this
> > worked on 8.x, but......
> > 
> > It seems that, because one of the things DisplayHandle can be is a pointer
> > value, and on 64 bit builds, that can (obviously!) be longer than 32 bits. But
> > Postscript only allows 32 bit number values, and these settings work through
> > the Postscript machinery, it needs to be compatible with that limitation.
> > 
> > So, on 64 bit systems the parameter for DisplayHandle is expected to be a
> > string, rather than an integer or a long. So, if you convert your DisplayHandle
> > parameter to a string, and use
> > 
> > -sDisplayHandle="handle value string"
> > 
> > 
> > That *might* help.
> 
> Did not work, tried -dDisplayHandle="0". The reason I brought this back up is
> that I installed 64 bit 8.71 and it failed with the same error. All my running
> installs are 32 bit, this is the first crack at 64 bit....

-sDisplayHandle="handle value string"
^^


Not -d.....


Comment 15


Dave Smith



2011-12-21 23:16:08 UTC

(In reply to comment #14)
> (In reply to comment #13)
> > (In reply to comment #12)
> > > I did, but with limited support for the display device, I only got it to run
> > > the file without the ICC profile error, I didn't try any further.
> > > 
> > > Now I have, and it seems there's a little "hiccup". I haven't a clue how this
> > > worked on 8.x, but......
> > > 
> > > It seems that, because one of the things DisplayHandle can be is a pointer
> > > value, and on 64 bit builds, that can (obviously!) be longer than 32 bits. But
> > > Postscript only allows 32 bit number values, and these settings work through
> > > the Postscript machinery, it needs to be compatible with that limitation.
> > > 
> > > So, on 64 bit systems the parameter for DisplayHandle is expected to be a
> > > string, rather than an integer or a long. So, if you convert your DisplayHandle
> > > parameter to a string, and use
> > > 
> > > -sDisplayHandle="handle value string"
> > > 
> > > 
> > > That *might* help.
> > 
> > Did not work, tried -dDisplayHandle="0". The reason I brought this back up is
> > that I installed 64 bit 8.71 and it failed with the same error. All my running
> > installs are 32 bit, this is the first crack at 64 bit....
> 
> -sDisplayHandle="handle value string"
> ^^
> 
> 
> Not -d.....

Good news and bad news...

From the command line no errors.
When I try to call it from the GS API (so in my case) I get

Unrecoverable error: rangecheck in .putdeviceprops

This is the case in my working 32 bit version and the 64 bit ...


Comment 16


Chris Liddell (chrisl)



2011-12-21 23:39:40 UTC

(In reply to comment #15)
> 
> Good news and bad news...
> 
> From the command line no errors.
> When I try to call it from the GS API (so in my case) I get
> 
> Unrecoverable error: rangecheck in .putdeviceprops
> 
> This is the case in my working 32 bit version and the 64 bit ...

Well, you have a couple of options. Since you seem reasonably confident with such things, you could build yourself a debug build of the Ghostscript .so lib, and put a break point in display_put_params() and step through to find where/why it throws an error (assuming it is the display device put_params that throws the erro, and not the generic code).

OR, if you could throw together a simple test harness which reproduces how you are driving Ghostscript in your app, I, or one of us, can look into what's causing the error.

Clealy, *our* implementations work a bit differently, so aren't driving this stuff in the same way as yours.


Comment 17


Dave Smith



2011-12-22 08:30:17 UTC

(In reply to comment #16)
> (In reply to comment #15)
> > 
> > Good news and bad news...
> > 
> > From the command line no errors.
> > When I try to call it from the GS API (so in my case) I get
> > 
> > Unrecoverable error: rangecheck in .putdeviceprops
> > 
> > This is the case in my working 32 bit version and the 64 bit ...
> 
> Well, you have a couple of options. Since you seem reasonably confident with
> such things, you could build yourself a debug build of the Ghostscript .so lib,
> and put a break point in display_put_params() and step through to find
> where/why it throws an error (assuming it is the display device put_params that
> throws the erro, and not the generic code).
> 
> OR, if you could throw together a simple test harness which reproduces how you
> are driving Ghostscript in your app, I, or one of us, can look into what's
> causing the error.
> 
> Clealy, *our* implementations work a bit differently, so aren't driving this
> stuff in the same way as yours.

I finally figured out what the difference between -s and -d mean and it works fine. 

May I suggest that the documentation here 
http://ghostscript.com/doc/current/API.htm#display

be updated from 

The callbacks are for device open, close, resize, sync, page, memory allocation and updating. Each callback function contains a handle can be set using

    -dDisplayHandle=1234 

to 

 -sDisplayHandle=1234 

and 

this code fragment

sprintf(arg2, "-dDisplayHandle=%d", 0);

be changed to 

sprintf(arg2, "-sDisplayHandle=%d", 0);


From the source code this seems to be the preferred way and for me it works on both 32 bit and 64 bit ghostscript, from versions 8.64 upwards ...


Comment 18


Chris Liddell (chrisl)



2011-12-22 08:36:10 UTC

Great, thanks for confirming.

I'll look at updating the documentation before the next release (note: the correct information is actually in gdevdsp.h - I'd always suggest checking relevant header files, since documentation does tend to rot over time).

*** This bug has been marked as a duplicate of bug 692532 ***

paustian

convert failing on conversion from .ps to .png

I think I know what is causing this, but for the life of me I cannot track down how to fix it.

I want to use convert as part of rendering equations spit out by Latex. I am using class.latexrender.php, So I downloaded all the software I need for this, using fink on mac OS X 10.5. Anyhow it seems as if everything is working up until the point the convert needs to do its thing. The php latex class then issues a command to convert the image like so.

Code: Select all

/sw/bin/convert -density 1.2 -trim -transparent "#FFFFFF" fe8e798694ec45f6e96f33e84f350b5c.ps fe8e798694ec45f6e96f33e84f350b5c.png

This fails. If I run it on the command line I get the following error.

Unrecoverable error: rangecheck in .putdeviceprops
Unrecoverable error: rangecheck in .putdeviceprops
convert: Postscript delegate failed `fe8e798694ec45f6e96f33e84f350b5c.ps’: No such file or directory.
convert: missing an image filename `fe8e798694ec45f6e96f33e84f350b5c.png’.

I know the file convert is trying to work on is there. From googling around it seems this is a ghostscript error. I know ghostscript is installed, here are the versions of the programs.
convert
Version: ImageMagick 6.4.1 09/29/09 Q16 http://www.imagemagick.org
Copyright: Copyright (C) 1999-2008 ImageMagick Studio LLC

ghostscript
GPL Ghostscript 8.61 (2007-11-21)
Copyright (C) 2007 Artifex Software, Inc. All rights reserved.
This software comes with NO WARRANTY: see the file PUBLIC for details.

Both were installed using fink. Btw I set this up on a test server and was able to get it running.

Any help is appreciated.

User avatar

fmw42

Posts: 25562
Joined: 2007-07-02T17:14:51-07:00
Authentication code: 1152
Location: Sunnyvale, California, USA

Re: convert failing on conversion from .ps to .png

Post

by fmw42 » 2009-09-29T20:10:27-07:00

looks like your delegates are not where IM thinks they should be. type

convert -list configure

look at line starting with DELEGATES. See if it includes gs and png. If not, then IM does not know where you installed GS and PNG delegate libraries.

Did you install IM with FINK? If not that would answer it as FINK puts stuff in its own special directory.

P.S. I am on a Mac OSX Tiger and install manually as both FINK and MacPorts puts things in their own special directories. But more important, you may not be able to find or find current versions of things you want to install from their libraries. So installing manually allows you to use the latest versions whenever you want rather than waiting for FINK or MacPorts to get their binaries in order.

paustian

Re: convert failing on conversion from .ps to .png

Post

by paustian » 2009-09-30T06:24:01-07:00

Thanks a bunch for the reply. I took another whack at it and finally cracked it. It was two problems. The first was that convert did not like my -density value. In face (hits palm on forehead) it was telling me so with the rangecheck warning. If you look at the convert manual -density it appears as if 1.2 would clearly be out of range.

So I fixed that problem in the php latex class. I then had the problem, as you suggest that convert cannot find gs. What it boiled down to was that /sw/bin was not in the PATH. I added a setenv(‘PATH=/sw/bin’) to the latex class and it worked. However I am not really happy with this solution as it seems a bit of a kludge. Any suggestions on how I can set up my environment so that the www user has /sw/bin in its path?

Anyhow it works for now.

Steve

I know next to nothing about MATLAB. I have three MATLAB modules developed by one of our scientists. Using MATLAB Builder JA, I have created Java libraries and these libraries are at the core of three RESTful services running on Tomcat6 using MCR. All three modules produce a slew of plots which are stored as either JPEG or PNG. All three call the «saveas» function to store the plots. On a non-headless Linux server, either Ubuntu 12.04, RHEL6 or CentOS 6.5, all three run as expected and produce the requested plots. On a headless server, again running either Ubuntu 12.04, RHEL6 or CentOS 6.5, two out of three run fine. The third always crashes and reports the following:

Error using ghostscript (line 186)

Problem converting PostScript. System returned error: -1.

Failed to convert to output format;

Ghostscript status: -15.Unrecoverable error: rangecheck in .putdeviceprops

rangecheck

Error in print>LocalPrint (line 305)

Error in print (line 231)

Error in saveas (line 169)

Error in PAtool_sliding_window_analysis (line 616)

file /usr/local/MATLAB/MATLAB_Compiler_Runtime/v82/mcr/toolbox/matlab/graphics/private/ghostscript.m, name ghostscript, line 186.

file /usr/local/MATLAB/MATLAB_Compiler_Runtime/v82/mcr/toolbox/matlab/graphics/print.m, name LocalPrint, line 305.

file /usr/local/MATLAB/MATLAB_Compiler_Runtime/v82/mcr/toolbox/matlab/graphics/print.m, name print, line 231.

file /usr/local/MATLAB/MATLAB_Compiler_Runtime/v82/mcr/toolbox/matlab/general/saveas.m, name saveas, line 169.

file /home/iaiadmin/.mcrCache8.2/jpa_DF0/PDS/CharTools/JPA/PAtool_sliding_window_analysis.m, name PAtool_sliding_window_analysis, line 616.

The «saveas» function is called like this:

saveas(gcf, ‘/home/someuser/output/data/plot.png’);

Does anyone have an idea as to what may be going wrong? Running on a non-headless server is fine for development, but I really need to have this working on a headless server.

Any help would be greatly appreciated. Thanks.


Answers (0)

See Also

Categories

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

An Error Occurred

Unable to complete the action because of changes made to the page. Reload the page to see its updated state.

When I try to print ODT or PDF or something else, the printer prints only:
unrecoverable error: rangecheck in .putdeviceprops and error message in /var/log/cups/error_log is:

E [21/Dec/2021:11:59:25 +0100] [Job 496] Job stopped due to filter errors; please consult the /var/log/cups/error_log file for details.

Log from: cat /var/log/cups/error_log:

E [21/Dec/2021:11:59:25 +0100] [Job 496] Job stopped due to filter errors; please consult the /var/log/cups/error_log file for details.
D [21/Dec/2021:11:59:25 +0100] [Job 496] The following messages were recorded from 11:59:13 to 11:59:25
D [21/Dec/2021:11:59:25 +0100] [Job 496] Applying default options...
D [21/Dec/2021:11:59:25 +0100] [Job 496] Adding start banner page "none".
D [21/Dec/2021:11:59:25 +0100] [Job 496] Adding end banner page "none".
D [21/Dec/2021:11:59:25 +0100] [Job 496] File of type application/vnd.cups-pdf-banner queued by "tomas".
D [21/Dec/2021:11:59:25 +0100] [Job 496] hold_until=0
D [21/Dec/2021:11:59:25 +0100] [Job 496] Queued on "Photosmart-B110" by "tomas".
D [21/Dec/2021:11:59:25 +0100] [Job 496] time-at-processing=1640084353
D [21/Dec/2021:11:59:25 +0100] [Job 496] 3 filters for job:
D [21/Dec/2021:11:59:25 +0100] [Job 496] bannertopdf (application/vnd.cups-pdf-banner to application/pdf, cost 32)
D [21/Dec/2021:11:59:25 +0100] [Job 496] pdftopdf (application/pdf to application/vnd.cups-pdf, cost 66)
D [21/Dec/2021:11:59:25 +0100] [Job 496] foomatic-rip (application/vnd.cups-pdf to printer/Photosmart-B110, cost 0)
D [21/Dec/2021:11:59:25 +0100] [Job 496] job-sheets=none,none
D [21/Dec/2021:11:59:25 +0100] [Job 496] argv[0]="Photosmart-B110"
D [21/Dec/2021:11:59:25 +0100] [Job 496] argv[1]="496"
D [21/Dec/2021:11:59:25 +0100] [Job 496] argv[2]="tomas"
D [21/Dec/2021:11:59:25 +0100] [Job 496] argv[3]="Testovací stránka"
D [21/Dec/2021:11:59:25 +0100] [Job 496] argv[4]="1"
D [21/Dec/2021:11:59:25 +0100] [Job 496] argv[5]="job-uuid=urn:uuid:ed884279-c10e-3377-5f28-7d6ee73b5fb7 job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1640084353 time-at-processing=1640084353"
D [21/Dec/2021:11:59:25 +0100] [Job 496] argv[6]="/var/spool/cups/d00496-001"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[0]="CUPS_CACHEDIR=/var/cache/cups"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[1]="CUPS_DATADIR=/usr/share/cups"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[2]="CUPS_DOCROOT=/usr/share/cups/doc-root"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[3]="CUPS_FONTPATH=/usr/share/cups/fonts"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[4]="CUPS_REQUESTROOT=/var/spool/cups"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[5]="CUPS_SERVERBIN=/usr/lib/cups"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[6]="CUPS_SERVERROOT=/etc/cups"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[7]="CUPS_STATEDIR=/run/cups"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[8]="HOME=/var/spool/cups/tmp"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[9]="PATH=/usr/lib/cups/filter:/usr/bin:/usr/sbin:/bin:/usr/bin"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[10]="SERVER_ADMIN=root@tomas-Dell-5590"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[11]="SOFTWARE=CUPS/2.3.1"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[12]="TMPDIR=/var/spool/cups/tmp"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[13]="USER=root"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[14]="CUPS_MAX_MESSAGE=2047"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[15]="CUPS_SERVER=/run/cups/cups.sock"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[16]="CUPS_ENCRYPTION=IfRequested"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[17]="IPP_PORT=631"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[18]="CHARSET=utf-8"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[19]="LANG=cs_CZ.UTF-8"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[20]="PPD=/etc/cups/ppd/Photosmart-B110.ppd"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[21]="RIP_MAX_CACHE=128m"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[22]="CONTENT_TYPE=application/vnd.cups-pdf-banner"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[23]="DEVICE_URI=socket://192.168.0.99:9100"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[24]="PRINTER_INFO=Photosmart B110c"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[25]="PRINTER_LOCATION="
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[26]="PRINTER=Photosmart-B110"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[27]="PRINTER_STATE_REASONS=none"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[28]="CUPS_FILETYPE=document"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[29]="FINAL_CONTENT_TYPE=application/vnd.cups-pdf"
D [21/Dec/2021:11:59:25 +0100] [Job 496] envp[30]="AUTH_I****"
D [21/Dec/2021:11:59:25 +0100] [Job 496] Started filter /usr/lib/cups/filter/bannertopdf (PID 33676)
D [21/Dec/2021:11:59:25 +0100] [Job 496] Started filter /usr/lib/cups/filter/pdftopdf (PID 33677)
D [21/Dec/2021:11:59:25 +0100] [Job 496] Started filter /usr/lib/cups/filter/foomatic-rip (PID 33680)
D [21/Dec/2021:11:59:25 +0100] [Job 496] Started backend /usr/lib/cups/backend/socket (PID 33681)
D [21/Dec/2021:11:59:25 +0100] [Job 496] STATE: +connecting-to-device
D [21/Dec/2021:11:59:25 +0100] [Job 496] Looking up "192.168.0.99"...
D [21/Dec/2021:11:59:25 +0100] [Job 496] STATE: -connecting-to-device
D [21/Dec/2021:11:59:25 +0100] [Job 496] 192.168.0.99=192.168.0.99
D [21/Dec/2021:11:59:25 +0100] [Job 496] pdftopdf: Last filter determined by the PPD: foomatic-rip; FINAL_CONTENT_TYPE: application/vnd.cups-pdf => pdftopdf will log pages in page_log.
D [21/Dec/2021:11:59:25 +0100] [Job 496] Calling FindDeviceById(cups-Photosmart-B110)
D [21/Dec/2021:11:59:25 +0100] [Job 496] Found device /org/freedesktop/ColorManager/devices/cups_Photosmart_B110
D [21/Dec/2021:11:59:25 +0100] [Job 496] Calling org.freedesktop.ColorManager.Device.Get(ProfilingInhibitors)
D [21/Dec/2021:11:59:25 +0100] [Job 496] PDF template file doesn't have form. It's okay.
D [21/Dec/2021:11:59:25 +0100] [Job 496] 'CM Color Calibration' Mode in SPOOLER-LESS: Off
D [21/Dec/2021:11:59:25 +0100] [Job 496] Getting input from file 
D [21/Dec/2021:11:59:25 +0100] [Job 496] foomatic-rip version 1.27.4 running...
D [21/Dec/2021:11:59:25 +0100] [Job 496] Parsing PPD file ...
D [21/Dec/2021:11:59:25 +0100] [Job 496] Added option ColorSpace
D [21/Dec/2021:11:59:25 +0100] [Job 496] Added option PageSize
D [21/Dec/2021:11:59:25 +0100] [Job 496] Added option ImageableArea
D [21/Dec/2021:11:59:25 +0100] [Job 496] Added option PaperDimension
D [21/Dec/2021:11:59:25 +0100] [Job 496] Added option ColorMode
D [21/Dec/2021:11:59:25 +0100] [Job 496] Added option Quality
D [21/Dec/2021:11:59:25 +0100] [Job 496] Added option RenderType
D [21/Dec/2021:11:59:25 +0100] [Job 496] Added option Font
D [21/Dec/2021:11:59:25 +0100] [Job 496] Parameter Summary
D [21/Dec/2021:11:59:25 +0100] [Job 496] -----------------
D [21/Dec/2021:11:59:25 +0100] [Job 496] Spooler: cups
D [21/Dec/2021:11:59:25 +0100] [Job 496] Printer: Photosmart-B110
D [21/Dec/2021:11:59:25 +0100] [Job 496] Shell: /bin/sh
D [21/Dec/2021:11:59:25 +0100] [Job 496] PPD file: /etc/cups/ppd/Photosmart-B110.ppd
D [21/Dec/2021:11:59:25 +0100] [Job 496] ATTR file: 
D [21/Dec/2021:11:59:25 +0100] [Job 496] Printer model: HP PhotoSmart P100 Foomatic/pjxl300
D [21/Dec/2021:11:59:25 +0100] [Job 496] Job title: Testovací stránka
D [21/Dec/2021:11:59:25 +0100] [Job 496] File(s) to be printed:
D [21/Dec/2021:11:59:25 +0100] [Job 496] <STDIN>
D [21/Dec/2021:11:59:25 +0100] [Job 496] Ghostscript extra search path ('GS_LIB'): /usr/share/cups/fonts
D [21/Dec/2021:11:59:25 +0100] [Job 496] Printing system options:
D [21/Dec/2021:11:59:25 +0100] [Job 496] Pondering option 'job-uuid=urn:uuid:ed884279-c10e-3377-5f28-7d6ee73b5fb7'
D [21/Dec/2021:11:59:25 +0100] [Job 496] Unknown option job-uuid=urn:uuid:ed884279-c10e-3377-5f28-7d6ee73b5fb7.
D [21/Dec/2021:11:59:25 +0100] [Job 496] Pondering option 'job-originating-host-name=localhost'
D [21/Dec/2021:11:59:25 +0100] [Job 496] Unknown option job-originating-host-name=localhost.
D [21/Dec/2021:11:59:25 +0100] [Job 496] Pondering option 'date-time-at-creation='
D [21/Dec/2021:11:59:25 +0100] [Job 496] Unknown option date-time-at-creation=.
D [21/Dec/2021:11:59:25 +0100] [Job 496] Pondering option 'date-time-at-processing='
D [21/Dec/2021:11:59:25 +0100] [Job 496] Unknown option date-time-at-processing=.
D [21/Dec/2021:11:59:25 +0100] [Job 496] Pondering option 'time-at-creation=1640084353'
D [21/Dec/2021:11:59:25 +0100] [Job 496] Unknown option time-at-creation=1640084353.
D [21/Dec/2021:11:59:25 +0100] [Job 496] Pondering option 'time-at-processing=1640084353'
D [21/Dec/2021:11:59:25 +0100] [Job 496] Unknown option time-at-processing=1640084353.
D [21/Dec/2021:11:59:25 +0100] [Job 496] CM Color Calibration Mode in CUPS: Off
D [21/Dec/2021:11:59:25 +0100] [Job 496] Options from the PPD file:
D [21/Dec/2021:11:59:25 +0100] [Job 496] ================================================
D [21/Dec/2021:11:59:25 +0100] [Job 496] File: <STDIN>
D [21/Dec/2021:11:59:25 +0100] [Job 496] ================================================
D [21/Dec/2021:11:59:25 +0100] [Job 496] PID 33676 (/usr/lib/cups/filter/bannertopdf) exited with no errors.
D [21/Dec/2021:11:59:25 +0100] [Job 496] PDF interactive form and annotation flattening done via QPDF
D [21/Dec/2021:11:59:25 +0100] [Job 496] PAGE: 1 1
D [21/Dec/2021:11:59:25 +0100] [Job 496] Filetype: PDF
D [21/Dec/2021:11:59:25 +0100] [Job 496] Storing temporary files in /tmp
D [21/Dec/2021:11:59:25 +0100] [Job 496] PID 33677 (/usr/lib/cups/filter/pdftopdf) exited with no errors.
D [21/Dec/2021:11:59:25 +0100] [Job 496] hrDeviceDesc="Photosmart B110c"
D [21/Dec/2021:11:59:25 +0100] [Job 496] prtMarkerColorantValue.1.1 = "black ink"
D [21/Dec/2021:11:59:25 +0100] [Job 496] ATTR: marker-colors=none,none,none,none
D [21/Dec/2021:11:59:25 +0100] [Job 496] ATTR: marker-names='"black ink"','"yellow ink"','"cyan ink"','"magenta ink"'
D [21/Dec/2021:11:59:25 +0100] [Job 496] ATTR: marker-types=ink,ink,ink,ink
D [21/Dec/2021:11:59:25 +0100] [Job 496] ATTR: marker-levels=15,58,0,0
D [21/Dec/2021:11:59:25 +0100] [Job 496] new_supply_state=8, change_state=ffff
D [21/Dec/2021:11:59:25 +0100] [Job 496] STATE: -developer-low-report
D [21/Dec/2021:11:59:25 +0100] [Job 496] STATE: -developer-empty-warning
D [21/Dec/2021:11:59:25 +0100] [Job 496] STATE: -marker-supply-low-report
D [21/Dec/2021:11:59:25 +0100] [Job 496] STATE: +marker-supply-empty-warning
D [21/Dec/2021:11:59:25 +0100] [Job 496] STATE: -opc-near-eol-report
D [21/Dec/2021:11:59:25 +0100] [Job 496] STATE: -opc-life-over-warning
D [21/Dec/2021:11:59:25 +0100] [Job 496] STATE: -toner-low-report
D [21/Dec/2021:11:59:25 +0100] [Job 496] STATE: -toner-empty-warning
D [21/Dec/2021:11:59:25 +0100] [Job 496] STATE: -waste-receptacle-almost-full-report
D [21/Dec/2021:11:59:25 +0100] [Job 496] STATE: -waste-receptacle-full-warning
D [21/Dec/2021:11:59:25 +0100] [Job 496] STATE: -cleaner-life-almost-over-report
D [21/Dec/2021:11:59:25 +0100] [Job 496] STATE: -cleaner-life-over-warning
D [21/Dec/2021:11:59:25 +0100] [Job 496] File contains 1 pages
D [21/Dec/2021:11:59:25 +0100] [Job 496] Starting renderer with command: gs -dShowAcroForm  -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -dNOMEDIAATTRS -dNOINTERPOLATE -r300x300 -sDEVICE=pjxl300 -dBitsPerPixel=1 -dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=842 -dPrintQuality=0 -dRenderType=0 -sOutputFile=-   /tmp/foomatic-KskjrT 
D [21/Dec/2021:11:59:25 +0100] [Job 496] Starting process "kid3" (generation 1)
D [21/Dec/2021:11:59:25 +0100] [Job 496] Starting process "kid4" (generation 2)
D [21/Dec/2021:11:59:25 +0100] [Job 496] Starting process "renderer" (generation 2)
D [21/Dec/2021:11:59:25 +0100] [Job 496] JCL: 33%-12345X@PJL
D [21/Dec/2021:11:59:25 +0100] [Job 496] <job data> 
D [21/Dec/2021:11:59:25 +0100] [Job 496] new_state=0, change_state=ffff
D [21/Dec/2021:11:59:25 +0100] [Job 496] STATE: -media-empty-warning
D [21/Dec/2021:11:59:25 +0100] [Job 496] STATE: -door-open-report
D [21/Dec/2021:11:59:25 +0100] [Job 496] STATE: -media-jam-warning
D [21/Dec/2021:11:59:25 +0100] [Job 496] STATE: -input-tray-missing-warning
D [21/Dec/2021:11:59:25 +0100] [Job 496] STATE: -output-tray-missing-warning
D [21/Dec/2021:11:59:25 +0100] [Job 496] STATE: -marker-supply-missing-warning
D [21/Dec/2021:11:59:25 +0100] [Job 496] STATE: -output-area-almost-full-report
D [21/Dec/2021:11:59:25 +0100] [Job 496] STATE: -output-area-full-warning
D [21/Dec/2021:11:59:25 +0100] [Job 496] backendWaitLoop(snmp_fd=5, addr=0x558cec64a9c8, side_cb=0x558ceb2586a0)
D [21/Dec/2021:11:59:25 +0100] [Job 496] renderer exited with status 255
D [21/Dec/2021:11:59:25 +0100] [Job 496] Connecting to 192.168.0.99:9100
D [21/Dec/2021:11:59:25 +0100] [Job 496] Kid3 exit status: 3
D [21/Dec/2021:11:59:25 +0100] [Job 496] PID 33680 (/usr/lib/cups/filter/foomatic-rip) stopped with status 9.
D [21/Dec/2021:11:59:25 +0100] [Job 496] Hint: Try setting the LogLevel to "debug" to find out more.
D [21/Dec/2021:11:59:25 +0100] [Job 496] Connecting to printer.
D [21/Dec/2021:11:59:25 +0100] [Job 496] STATE: -connecting-to-device
D [21/Dec/2021:11:59:25 +0100] [Job 496] Connected to printer.
D [21/Dec/2021:11:59:25 +0100] [Job 496] Connected to 192.168.0.99:9100...
D [21/Dec/2021:11:59:25 +0100] [Job 496] backendRunLoop(print_fd=0, device_fd=6, snmp_fd=5, addr=0x558cec64a9c8, use_bc=1, side_cb=0x558ceb2586a0)
D [21/Dec/2021:11:59:25 +0100] [Job 496] STATE: +cups-waiting-for-job-completed
D [21/Dec/2021:11:59:25 +0100] [Job 496] Waiting for printer to finish.
D [21/Dec/2021:11:59:25 +0100] [Job 496] prtMarkerSuppliesLevel.1.1 = 94
D [21/Dec/2021:11:59:25 +0100] [Job 496] prtMarkerSuppliesLevel.1.2 = 0
D [21/Dec/2021:11:59:25 +0100] [Job 496] prtMarkerSuppliesLevel.1.3 = 0
D [21/Dec/2021:11:59:25 +0100] [Job 496] prtMarkerSuppliesLevel.1.4 = 0
D [21/Dec/2021:11:59:25 +0100] [Job 496] ATTR: marker-levels=66,0,0,0
D [21/Dec/2021:11:59:25 +0100] [Job 496] new_supply_state=8, change_state=0
D [21/Dec/2021:11:59:25 +0100] [Job 496] new_state=0, change_state=0
D [21/Dec/2021:11:59:25 +0100] [Job 496] PAGE: total 1
D [21/Dec/2021:11:59:25 +0100] [Job 496] PID 33681 (/usr/lib/cups/backend/socket) exited with no errors.
D [21/Dec/2021:11:59:25 +0100] [Job 496] End of messages
D [21/Dec/2021:11:59:25 +0100] [Job 496] printer-state=3(idle)
D [21/Dec/2021:11:59:25 +0100] [Job 496] printer-state-message="Waiting for printer to finish."
D [21/Dec/2021:11:59:25 +0100] [Job 496] printer-state-reasons=marker-supply-empty-warning

I tried apt-purge: cups, ghostscript and reinstall them. Didn’t help.
I tried:

sudo rmdir /usr/share/ghostscript/9.25/iccprofiles
sudo apt-get install --reinstall libgs9-common

Didn’t help.

Printer:HP photosmart B110 connected through WIFI.
System: Ubuntu 20.04, all updates.
From Windows or from Android printer prints well.

Понравилась статья? Поделить с друзьями:
  • Unrecoverable error bombing out
  • Unrecoverable build error 0x80004005
  • Unrecoverable bootloader error 0x00000008 asus tf300tg
  • Unrecoverable bootloader error 0x00000000 asus
  • Unrecognized vm option maxpermsize 512m error could not create the java virtual machine