On Tue, Jul 09, 2013 at 04:01:22PM +0100, Brian Potkin wrote: > On Tue 09 Jul 2013 at 14:11:47 +0100, Brian Potkin wrote: > > > However, the Gutenprint and postscript driver both worked to produce > > an expected output in /tmp. This is reason enough to question whether > > No they didn't! I really should have checked the error log rather than > just the file types in /tmp and their sizes. The file from Gutenprint > was rather small, which also should have prompted me to look at the > logs. So pdftopdf crashes with the three PPDs. On the bright side, > textttopdf works and the rendering completed with no errors. :) > > Choosing a few random PPDs gives the same error. Back to 'grave' it, but > more testing wouldn't do any harm.
Did you get my other message where I said printing works after rebuilding the package locally? I'm not sure if it is worth it to track down which change in which library broke it. I don't print often so I can't tell when the issue started. The network printer actually printed a page with an error message from the filter pipeline (something about unable to open device), so I wasted a few pages before I had the idea to test with cups-PDF. There is always lots of cursing when CUPS breaks ;-) Thanks, Johannes -- To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130709155219.ga25...@sig21.net
