Bugzilla – Bug 520
foomatic-filters-4.0.5: failed to print with gdi driver (/bin/bash: -c: line 0: syntax error near unexpected token)
Last modified: 2010-09-14 04:01:29 UTC
After cups upgrade to 1.4.x and installation foomatic-filters-4.0.5, foomatic-db-4.0.20100913 and net-print/foomatic-db-engine-4.0.5 I'm unable to print on Samsung ML-1210 printer. Enabling cups debug reveals following error: D [13/Sep/2010:13:33:25 +0400] [Job 55] Starting renderer with command: "gs -sstdout=%stderr -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=gdi -dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=842 -r600x600 -sOutputFile=%stdout -c '/Default << /SpotFunction { 180 mul cos exch 180 mul cos add 2 div } bind /HalftoneType 1 /AccurateScreens true /Frequency 137 /Angle 37 /HalftoneName (Round Dot Screen) >> /Halftone defineresource sethalftone << /HalftoneMode 1 /UseWTS false /Accura -f -_ | perl -p -e 's/PJL PAGE LETTER/PJL PAGE A4/; s/PJL PAGE (\S*) AUTO/PJL PAGE $1 AUTO/; s/PJL SET TONERSAVE = OFF/PJL SET TONERSAVE = OFF\r\n\@PJL SET ECONOMODE = OFF/; s/PJL SET PAPERTYPE = NORMAL/PJL SET PAPERTYPE = NORMAL/; s/PJL SET DENSITY = 1/PJL SET DENSITY = 3/; s/(\@PJL ENTER LANGUAGE)/\@PJL SET RET = OFF\r\n$1/; s/(\@PJL ENTER LANGUAGE)/\@PJL SET JAMRECOVERY = ON\r\n$1/; s/(\@PJL ENTER LANGUAGE)/\@PJL SET REPRINT = ON\r\n$1/; s/(\@PJL ENTER LANGUAGE)/\@PJL SET ALTITUDE = OFF\r\n$1/; s/PJL COPIES = 1/PJL COPIES = 1/; s/(\@PJL ENTER LANGUAGE)/\@PJL DEFAULT TIM D [13/Sep/2010:13:33:25 +0400] [Job 55] EOUT = 15\r\n$1/; s/(\@PJL ENTER LANGUAGE)/\@PJL DEFAULT POWERSAVE = ON\r\n$1/; s/(\@PJL ENTER LANGUAGE)/\@PJL DEFAULT POWERSAVETIME = 5\r\n$1/; '" D [13/Sep/2010:13:33:25 +0400] [Job 55] Starting process "kid3" (generation 1) D [13/Sep/2010:13:33:25 +0400] [Job 55] Starting process "kid4" (generation 2) D [13/Sep/2010:13:33:25 +0400] [Job 55] Starting process "renderer" (generation 2) D [13/Sep/2010:13:33:25 +0400] [Job 55] JCL: %-12345X@PJL D [13/Sep/2010:13:33:25 +0400] [Job 55] <job data> D [13/Sep/2010:13:33:25 +0400] [Job 55] D [13/Sep/2010:13:33:25 +0400] [Job 55] /bin/bash: -c: line 0: syntax error near unexpected token `(' This is the error ^^^^^^^^^^^^^ D [13/Sep/2010:13:33:25 +0400] [Job 55] /bin/bash: -c: line 0: `gs -sstdout=%stderr -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=gdi -dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=842 -r600x600 -sOutputFile=%stdout -c '/Default << /SpotFunction { 180 mul cos exch 180 mul cos add 2 div } bind /HalftoneType 1 /AccurateScreens true /Frequency 137 /Angle 37 /HalftoneName (Round Dot Screen) >> /Halftone defineresource sethalftone << /HalftoneMode 1 /UseWTS false /Accura -f -_ | perl -p -e 's/PJL PAGE LETTER/PJL PAGE A4/; s/PJL PAGE (\S*) AUTO/PJL PAGE $1 AUTO/; s/PJL SET TONERSAVE = OFF/PJL SET TONERSAVE = OFF\r\n\@PJL SET ECONOMODE = OFF/; s/PJL SET PAPERTYPE = NORMAL/PJL SET PAPERTYPE = NORMAL/; s/PJL SET DENSITY = 1/PJL SET DENSITY = 3/; s/(\@PJL ENTER LANGUAGE)/\@PJL SET RET = OFF\r\n$1/; s/(\@PJL ENTER LANGUAGE)/\@PJL SET JAMRECOVERY = ON\r\n$1/; s/(\@PJL ENTER LANGUAGE)/\@PJL SET REPRINT = ON\r\n$1/; s/(\@PJL ENTER LANGUAGE)/\@PJL SET ALTITUDE = OFF\r\n$1/; s/PJL COPIES = 1/PJL COPIES = 1/; s/(\@PJL ENTER LANGUAGE)/\@PJL DEFAULT TIMEOUT = 15 D [13/Sep/2010:13:33:25 +0400] [Job 55] \r\n$1/; s/(\@PJL ENTER LANGUAGE)/\@PJL DEFAULT POWERSAVE = ON\r\n$1/; s/(\@PJL ENTER LANGUAGE)/\@PJL DEFAULT POWERSAVETIME = 5\r\n$1/; '' D [13/Sep/2010:13:33:25 +0400] [Job 55] renderer exited with status 2 D [13/Sep/2010:13:33:25 +0400] PID 16961 (/usr/libexec/cups/filter/foomatic-rip) did not catch or ignore signal 13. D [13/Sep/2010:13:33:25 +0400] PID 16960 (/usr/libexec/cups/filter/pstops) did not catch or ignore signal 13. D [13/Sep/2010:13:33:25 +0400] PID 16962 (/usr/libexec/cups/backend/usb) exited with no errors.
It seems that the PPD file of your existing print queue was not generated by the software which you have freshly installed. The problem which shows in your error_log is known and already fixed in Foomatic. Installing from source and from most distribution packages does not update PPD files of already existing print queues. Please update the PPD or remove and re-create the print queue. Then you will get a working PPD file.