Description of problem: certain postscript files can generate PCL6 errors on my samsung ML-1710 printer. the attached postscript file (also given in the URL) is an example that causes failure every time. it displays properly using ggv (or anything else that uses gs's X11 driver) and prints fine via the hpijs driver to my HP DJ960 or photosmart 7960 printers. if i attempt to print that file to the samsung, it prints out the following error message: PCL6 ERROR - FALSE POSITION : 0x6abadc (6994652) SYSTEM : WSIM/gdi LINE : 321 VERSION : QPDL 1.14 09-28-2002 this printer was configured under FC3 using system-config-printer which allowed me to specify the model as ML-1710. it works beautifully 99% of the time, but every now and then a file comes along that doesn't work. the samsung is connected to a d-link DP-300U lpd print server along with the HP DJ960. i filed this bug under foomatic because it appears to me to be a problem with incorrect PCL6 being generated, i.e. a driver issue. Version-Release number of selected component (if applicable): system-config-printer-0.6.116.1.1-1 foomatic-3.0.2-3 cups-1.1.22-0.rc1.8.5 How reproducible: with the provided postscript file, every time. Steps to Reproduce: 1. configure ML-1710 using system-config-printer 2. print provided postscript file to the ML-1710 3. Actual results: i get the error message given above. Expected results: i expected a correct printout of the page like i get with my other printers. Additional info:
Created attachment 111076 [details] a level 3 postscript document
First, the sample file is not Level 3 PostScript file. Number 3 in the header indicates conformance to DSC v. 3.0 . I can look into this issue providing Red Hat will support the project.
Please try this: ip=1.2.3.4 # use the IP address of your Samsung printer gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=gdi \ -sOutputFile=gdi.out GDI_test.ps cat gdi.out > /dev/tcp/$ip/9100 Does that work?
No response from reporter to request for info for over a year. Also, FC3 is now the responsibility of Fedora Legacy and this is not a security bug. Closing.