When I print with cups using some foomatic postscript drivers I am not able to print with Double-Sided Printing as the default mode. After I set LogLevel debug in cups.conf I had this error: "D [18/Feb/2005:10:27:52 +0100] [Job 368] renderer command: level=0; printf "%!\n%%%% %%%%\n<</Duplex true /Tumble false>>setpagedevice\n"; if [ $level -gt 0 ]; then if [ $level -lt 99 ]; then level=" -dLanguageLevel=$level"; else level=""; fi; gs -q -dPARANOIDSAFER -dNOPAUSE -dBATCH -sDEVICE=pswrite$level -sOutputFile=- -; else cat; fi D [18/Feb/2005:10:27:52 +0100] [Job 368] sh: line 0: printf: `!': invalid format character" The drivers I tested was Xerox DocuPrint C55 Foomatic/postscript and HP LaserJet 4000 Foomatic/Postscript. Every time I try to print I always get single pages printed Reproducible: Always Steps to Reproduce: 1.choose cups as printing system 2.Add a printer with web wizard 3.choose the driver Xerox -> Xerox DocuPrint C55 Foomatic/Postscript (recommended) en 4. Go to web page "configure printer" of this printer 5. change "Double-sided Printing" in "Long Edge(Standard)" 6. Try to print to this printer I resolved this error changing this line in the ppd fiel created by cups for the printer Xerox: *FoomaticRIPCommandLine: "level=%D; printf "%%!\n%%%% %%%%\n%C&quo&& instead of *FoomaticRIPCommandLine: "level=%D; printf "%!\n%%%% %%%%\n%C&quo&& and this line in my Hp 4000 ppd: *FoomaticRIPCommandLine: "level=%D; printf "%%!\n%%%% %%%%\n%C&qu&& instead of *FoomaticRIPCommandLine: "level=%D; printf "%!\n%%%% %%%%\n%C&qu&& It should be fixed for all drivers affected in foomatic-db package.
I was experiencing the same situation (inability to print duplex under CUPS) on a Samsung ML-2152 Postscript printer. I made Riccardo's change to the FoomaticRIPCommandLine in my SamsungML.ppd file. Then the duplex printing worked correctly. NOTES: In my case, duplex printing used to work a some months ago. However, in trying to print duplex today, it didn't work. Perhaps in the interim there has been a change to the renderer or to the PPD file that I emerged. I mention this in case it helps identify why duplex stopped working in my case and pinpoint the cause. Over the last several months, I have updated CUPS as new ebuilds have been released from 1.1.21 through 1.1.23-r1, most recently on March 9, 2005. Duplex used to work for me under 1.1.21. I updated foomatic-db-engine most recently on February 27, 2005.
Riccardo: which cups version are you using?
This bug was resolved upstream with foomatic-db-20050430. Since foomatic-db-20050606 is in the portage tree, is this still an issue?
Thanks, fixed as per comment #3