After upgrading on 20060414 nothing really changed (probably, because the configuration file will not be overwritten), I got rid of it by accident though:
While trying to set up Dapper as print server for some WindowsXP workstations I came to edit the CUPS config file via http://localhost:631/admin?op=config-server and, while being dissatisfied with my results, I chose the option "Use Default Configuration File".
The generated file looks distinctly different from what is delivered with the distribution and the reported problem is gone with it.
I have a Canon iP4000 as well as the PDF-Printer working now also from the WindowsXP workstations over SAMBA. In fact, I am using the CUPS supplied Default Configuration File without changes.
After upgrading on 20060414 nothing really changed (probably, because the configuration file will not be overwritten), I got rid of it by accident though:
While trying to set up Dapper as print server for some WindowsXP workstations I came to edit the CUPS config file via http:// localhost: 631/admin? op=config- server and, while being dissatisfied with my results, I chose the option "Use Default Configuration File".
The generated file looks distinctly different from what is delivered with the distribution and the reported problem is gone with it.
I have a Canon iP4000 as well as the PDF-Printer working now also from the WindowsXP workstations over SAMBA. In fact, I am using the CUPS supplied Default Configuration File without changes.