On Wed 19 Jul 2017 at 09:40:11 +0200, Christoph Pleger wrote: > Hello, > > >But I dug a hole for myself. > > > >4. Reinstall stretch's cups-browsed (no change in cupsd.conf) to go back > > to 2. "OpPolicy authenticated" is what I get! > > > >5. Remove "DefaultPolicy authenticated" from cupsd.conf. Back to 1. Not > > at all! It's still "DefaultPolicy authenticated". > > > >Colour me perplexed (or inept). > > I guess that some information is taken from the files in /var/cache/cups and > that these cache files are not correctly updated ...
cups-browsed now saves a copy of the remote printer's PPD in /var/cache/cups. "Operation Policy" is one of the options which can set there using the web interface (say). I wonder whether we really have a bug here if this is the way it is designed to work now. Regards, Brian.