Hello Tanguy, Tanguy Ortolo [2010-06-14 12:47 +0200]: > I do. Though I really do not want to print hundreds of test pages, and > would rather print to files, using… a custom backend (unless a file > backend already exists, but I never saw one, but maybe such a – very > simple, but very useful for debugging – backend may be worth packaging). That does exist. Set "FileDevice Yes" in cupsd.conf (see man cupsd.conf), and as a device name use something like file:///tmp/cups.out; I haven't tried that for a while, but back then it worked fine. For postscript output you can of course use the result right away. For raster data there's a nice viewer out there [1], but it's not packaged. But I guess for most problems ("doesn't print", etc.) you just need to look whether it produces some output in the first place, rather than just crashing. Asking verbose cups error_log files from reporters is very helpful with that (cupsctl --debug-logging), as it will show you the precise command lines of all filters. These can then be called manually and checked their individual results. Thanks for your interest! Martin [1] http://www.easysw.com/~mike/rasterview/index.html -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
Attachment:
signature.asc
Description: Digital signature