"statusdict begin product end" is not properly detected as it returns "GNU Ghostscript" instead of the expected "Ghostscript". The postscript files can be fixed in /usr/share/ghostscript/4.03 : *** stcinfo.ps.orig Thu Dec 3 22:56:43 1998 --- stcinfo.ps Thu Dec 3 22:57:54 1998 *************** *** 30,36 **** % use either existing STCinfo-dictionary, retrieve new one or create dummy statusdict begin product end ! dup (Ghostscript) eq exch (Aladdin Ghostscript) eq or{ currentdevice getdeviceprops .dicttomark dup /Name get (stcolor) eq /STCi_onstc exch def --- 30,37 ---- % use either existing STCinfo-dictionary, retrieve new one or create dummy statusdict begin product end ! dup (Ghostscript) eq exch dup (Aladdin Ghostscript) eq exch ! (GNU Ghostscript) eq or or{ currentdevice getdeviceprops .dicttomark dup /Name get (stcolor) eq /STCi_onstc exch def *** stcolor.ps.orig Thu Dec 3 22:56:43 1998 --- stcolor.ps Thu Dec 3 22:57:54 1998 *************** *** 31,38 **** % a message is send to the output. If this message bothers you, remove it, % but I prefer to know why the device-setup failed. ! statusdict begin product end ! dup (Ghostscript) eq exch (Aladdin Ghostscript) eq or{ % fetch the current device-parameters this is specific for Ghostscript. --- 31,39 ---- % a message is send to the output. If this message bothers you, remove it, % but I prefer to know why the device-setup failed. ! statusdict begin product end ! dup (Ghostscript) eq exch dup (Aladdin Ghostscript) eq exch ! (GNU Ghostscript) eq or or{ % fetch the current device-parameters this is specific for Ghostscript.
I don't have such a printer to evaluate this patch.
We will need to get one of these printers into the test lab to accurately test this problem.
Commits pushed to master at https://github.com/openshift/openshift-ansible https://github.com/openshift/openshift-ansible/commit/c2622f7e98cfde295392fc96cc6e5999adfca283 resolves issue #289 https://github.com/openshift/openshift-ansible/commit/e052839a463f3c09a9a31bd6d4a1fa4bc2a267f0 Merge pull request #290 from cooktheryan/atomic-exclude resolves issue #289