This is just to confirm that this problem persists. I am currently using foomatic-db-compressed-ppds_20141016-1_all.deb
It happens with all my debian testing machines whether accessed via usb or parallel port. As my previous reports have suggested it has seemed a little non deterministic in the past, but seems pretty solid just now. After printing the firts page, it seems that there is some escape sequence which is fouled up so that it treats the @PJL commands as text to be printed rather than control sequences. I am pretty sure that this happened several years ago. all used to be fine, but I wonder if the reimplentation vis xml (is that right?) had a problem. Anyway, it is time that I/we got to the bottom of this. Is there any information or debugging that I can do here, or should I reach for gdb and sources? The only message that might have some relevance in /var/log/cups/error.log is E [18/Oct/2014:15:19:45 +0100] [CGI] Unable to scan "@LOCAL"! but the time stamp suggests that was before I printed anything. Meanwhile I will capture the data stream sent to the printer and see whether I can spot the problem. If it is not obvious, I will attach the files to a later message if they are not too large. ael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org