Comment 20 for bug 420490

I can now print with the normal printer as well, but I'm a bit unsure why. I moved /var/cache/cups/xrxwest.ipp out of the way and restarted cups, which seems to magically allow me to print, but the xrxwest.ipp that got created in its place is the same bit for bit.

This would mean that using a generic postscript driver worked simply because I added a new printer for it.

Does this make any sense?

I now have in /var/cache/cups:
   4 drwxrwxr-x 3 root lp 4096 2009-10-08 14:47 .
   4 drwxr-xr-x 24 root root 4096 2009-09-27 20:03 ..
  12 -rw------- 1 root lp 11855 2009-10-08 14:49 10.87.5.15.snmp
   4 -rw-r--r-- 1 root root 824 2009-10-08 14:30 Generic-PostScript-Printer.ipp
 152 -rw------- 1 lp lp 147885 2009-10-08 13:47 help.index
   4 -rw-r----- 1 root lp 2239 2009-10-08 14:50 job.cache
8684 -rw------- 1 lp lp 8876004 2009-10-05 09:32 ppds.dat
   4 -rw-r----- 1 root lp 75 2009-10-08 14:50 remote.cache
   4 drwxrwxr-x 2 root lp 4096 2008-10-20 08:59 rss
   4 -rw-r--r-- 1 root root 1546 2009-09-20 17:43 xrxcontrol.ipp
   4 -rw-r--r-- 1 root root 1546 2009-10-08 14:47 xrxwest.ipp
   4 -rw-r--r-- 1 root root 1546 2009-09-20 17:43 xrxwest.ipp.orig

Notice the mix of lp/root ownership.