When I go to http://localhost:631, and add a new printer, I choose "HP" as the brand name, but in the printer model listing that follows, only the gimp-print drivers are shown. None of the foomatic (hpijs, Postscript, etc...) drivers are shown. This is broken behaviour (I think). At least I know that in Debian, you can see ALL drivers there right away on a fresh install without doing any extra config. Since I cannot add my printer using this GUI, I do this from the command line instead: foomatic-configure -s cups -p HP-LaserJet_2200 -c smb://dgrant:password@venus/sidic-hp -n HP2200 -d Postscript However, I know this HP-LaserJet_2200 model with Postscript driver is on my hard drive as it was installed/created by foomatic... I think CUPS just doesn't know where they are for some reason? In my /usr/share/cups/model directory, I see this: total 112 -rw-r--r-- 1 root root 9497 Aug 2 16:21 deskjet.ppd -rw-r--r-- 1 root root 10177 Aug 2 16:21 deskjet2.ppd -rw-r--r-- 1 root root 7893 Aug 2 16:21 dymo.ppd -rw-r--r-- 1 root root 5894 Aug 2 16:21 epson24.ppd -rw-r--r-- 1 root root 5711 Aug 2 16:21 epson9.ppd lrwxrwxrwx 1 root root 14 Aug 2 16:24 foomatic-ppds -> /usr/share/ppd drwxr-xr-x 3 root root 4096 Aug 1 20:10 gimp-print -rw-r--r-- 1 root root 9460 Aug 2 16:21 laserjet.ppd -rw-r--r-- 1 root root 5494 Aug 2 16:21 okidat24.ppd -rw-r--r-- 1 root root 5314 Aug 2 16:21 okidata9.ppd -rw-r--r-- 1 root root 5656 Aug 2 16:21 stcolor.ppd -rw-r--r-- 1 root root 5671 Aug 2 16:21 stcolor2.ppd -rw-r--r-- 1 root root 5647 Aug 2 16:21 stphoto.ppd -rw-r--r-- 1 root root 5662 Aug 2 16:21 stphoto2.ppd If you follow the foomatic-ppds symlink you will find the HP directory and a listing of PPDs using ALL possible printer-driver combinations. So CUPS just doesn't look there...I've looked at /etc/cups/ to see if I could find some config file where this is specified but I can't see anything. Reproducible: Always Steps to Reproduce:
USE=ppds emerge foomatic-db please take a look at the comments printed after emerging new packages next time ;)
Thanks, but I have all USE flags for all the foomatic and cups packages turned on in make.conf. That includes PPDS. I always use emerge -vp before I emerge, so I know which flags are useful. I just re-emerged all the foomatic packages as well as cups earlier today before I filed this bug, and still no change.
did u restart cups?
Damn, good idea. Should cupsd be restarted when cups is emerged?
[19:30:38] <lanius> if you update service, e.g. cups, should it be restarted, like debian does? [19:31:10] <brad[]> no [19:31:35] <lanius> just a no, because it currently isn't done or a general no? [19:31:48] <brad[]> The service may require additional modifications to configuration files, restarting them automatically could cause them to fail without human intervention [19:31:50] <lisa> distccd is not restarted [19:32:35] <g2boojum> lanius: Gentoo policy is that ebuilds do not start/stop/restart services.
Cool, it works now. I had to do /etc/init.d/cupsd zap and then when I restarted cups it started using a lot of CPU so I knew it was working now! Is this a new feature since we got the new foomatic packages? I don't think this was even possible with the old foomatic package. Anyways, thanks to whoever got this cups-foomatic stuff all working in the new packages. I don't think Debian's ever worked this good, because Debian doesn't have all printer/driver combinations.
yes, there were some fine cleanups in the new foomatic 3 packages :)
Could there be an einfo message on post_rm() for foomatic which says "restart cups"?
