Description of problem: Client machines on the network weren't getting Browsed
queues until I changed BrowseAddress on the server from 255.255.255.255 to
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start system-config-printer on a local client
2. don't observe Browsed queues
3. edit BrowseAddress line in /etc/cups/cupsd.conf on the server to use @LOCAL
and re-start cupsd
4. restart system-config-printer on a local client and observe Browsed queues as
Additional info: The bug is that subsequent uses of system-config-printer will
overwrite cupsd.conf with the useless default BrowseAddress.
It seems that a (virtual) printer was configured to have All (the default!) as the
Browse Allow address and this has the effect of producing 255.255.255.255 as the
only BrowseAddress. That is, allowing anyone to Browse one printer ensures that
no printer can be browsed locally. Is this your intention? How about some
sensible defaults like @LOCAL for the BrowseAddress. How about allowing
more than one BrowseAddress.
The re-written system-config-printer no longer edits BrowseAddress lines in
cupsd.conf unless explicitly told to, just like the CUPS web interface.