On Saturday 20 December 2008 11:37:32 Peter Humphrey wrote: > These are the USE flags I installed CUPS with: > > [ebuild R ] net-print/cups-1.3.9-r1 USE="acl dbus jpeg pam perl png > python ssl tiff > -X -avahi -gnutls -java -kerberos -ldap -php -ppds -samba -slp -static > -xinetd -zeroconf" LINGUAS="en -de -es -et -fr -he -id -it -ja -pl -sv > -zh_TW"
Since writing that I reasoned that cups might want the ppds USE flag, so I remerged it with that flag, after restoring the squeaky-clean system to a new file-system. Three foomatic packages were pulled in: $ grep completed /var/log/emerge.log | tail -n 4 1229776693: ::: completed emerge (1 of 4) net-print/foomatic-db-ppds-3.0.20060720 to / 1229776708: ::: completed emerge (2 of 4) net-print/foomatic-filters-3.0.20080507 to / 1229776740: ::: completed emerge (3 of 4) net-print/foomatic-filters-ppds-20070501 to / 1229776821: ::: completed emerge (4 of 4) net-print/cups-1.3.9-r1 to / Then I let cups detect the printer for itself, and gave it a PPD file I got from linuxprinting.org, and when I asked for a test page I got "/usr/libexec/cups/filter/foomatic-rip failed" and the job list showed it as Unknown Stopped. So I deleted the printer, let it redetect it, and this time gave it the PPD file it offered me: a DJ200 file, which I wouldn't have thought to use. This time on trying a test page I got "Printer is now on-line." but still nothing appeared on the printer. I did have this printer working some months ago, both locally and over the network, together with a Kyocera laser printer, but something has changed and I haven't yet worked out what. -- Rgds Peter
