Hi, Well, after many stupid trials and thanks to a lot of help by you and upstream, the most useful thing I can add is: 1. I isolated the command which seems to be a problem: gs -dQUIET -dPARANOIDSAFER -dNOPAUSE -dBATCH -dNOINTERPOLATE \ -dNOMEDIAATTRS -dShowAcroForm -sstdout=%stderr \ -sOutputFile=out.ras \ -sDEVICE=cups -r600x600 -dMediaPosition=1 -dDEVICEWIDTHPOINTS=595 \ -dDEVICEHEIGHTPOINTS=842 -dcupsBitsPerColor=1 -dcupsColorOrder=0 \ -dcupsColorSpace=3 -dcupsCompression=17 -scupsPageSizeName=A4 \ -I/usr/share/cups/fonts \ input.pdf
Result: D [18/Mar/2018:03:56:11 +0100] [Job 71] ./base/gsicc_manage.c:1148: gsicc_open_search(): Could not find default_gray.icc D [18/Mar/2018:03:56:11 +0100] [Job 71] | ./base/gsicc_manage.c:1799: gsicc_set_device_profile(): cannot find device profile D [18/Mar/2018:03:56:11 +0100] [Job 71] Unrecoverable error: rangecheck in .putdeviceprops 2. As requested, I created a simplified gs document, to test results without so much filters: gs -sDEVICE=tiff24nc -sOutputFile=out.tif input.pdf Here I get: default_grau.icc not found, gs says that it cannot find default_rgb.icc. and the initial error. Now upstream seems to say it is a Debian problem and I am out ou idea. Many thanks for further help Regards signature_jp_2 Logo Hypra JEAN-PHILIPPE MENGUAL DIRECTEUR TECHNIQUE ET QUALITÉ 102, rue des poissonniers, 75018, Paris Tel : +331 84 73 06 61 <tel:+33184730661> Mob : +336 76 34 93 37 <tel:+33676349337> jpmeng...@hypra.fr <mailto:jpmeng...@hypra.fr> www.hypra.fr <http://www.hypra.fr/> Facebook Hypra <https://www.facebook.com/hyprasoftware/> Twitter Hypra <https://twitter.com/Hypra_> Linkedin Jean-Philippe <https://fr.linkedin.com/in/jean-philippe-mengual-800133135> Le 27/03/2018 à 12:32, Brian Potkin a écrit : > On Sat 24 Mar 2018 at 19:37:37 +0000, Brian Potkin wrote: > >> tags 893332 moreinfo >> thanks >> >> >> On Sun 18 Mar 2018 at 04:55:38 +0100, Jean-Philippe MENGUAL wrote: >> >>> I try to print a test page from CUPS in a Samsung printer. >>> >>> * What exactly did you do (or not do) that was effective (or >>> ineffective)? >>> >>> See the log attached (see from line 3455), explaining what happens. I am >>> concerned by job 71 stuff. >>> >>> * What was the outcome of this action? >>> >>> The printing fails. >> Thank you for the report and the logs, Jean-Philippe. >> >> Your upstream report has received advice to follow. How did you go on with >> this? >> >> You have also posted to debian-user >> >> https://lists.debian.org/debian-user/2018/03/msg00662.html >> >> and advice was offered there. Is there any feedback to give? > Jean-Philippe has continued his conversation with upstream at > > https://bugs.ghostscript.com/show_bug.cgi?id=695873 > > (starting at comment 11) and added to the thread on debian-user. He has > been advised to update us on his progress in #893332. > > Regards, > > Brian. >
