Bug#909423: cups-browsed: Unusual behaviour with the default CreateIPPPrinterQueues

2018-11-27 Thread Brian Potkin
On Tue 27 Nov 2018 at 20:33:10 +0100, Till Kamppeter wrote:

> So to investigate this further I would need a log file of cups-browsed.
> 
> You get a log file if there is a line
> 
> DebugLogging file
> 
> in cups-browsed.conf
> 
> The log file will by default be created as
> 
> /var/log/cups/cups-browsed_log
> 
> Please attach your log file (from starting cups-browsed until observation of
> wrong behavior) to this bug report. Also attach your cups-browsed.conf.

I gave a log file already, but have no problem in attaching another one.

Cheers,

Brian.
# All configuration options described here can also be supplied on the
# command line of cups-browsed via the "-o" option. In case of
# contradicting settings the setting defined in the configuration file
# will get used.

# Unknown directives are ignored, also unknown values.


# Where should cups-browsed save information about the print queues it had
# generated when shutting down, like whether one of these queues was the
# default printer, or default option settings of the queues?

# CacheDir /var/cache/cups


# Where should cups-browsed create its debug log file (if "DebugLogging file"
# is set)?

LogDir /var/log/cups


# How should debug logging be done? Into the file
# /var/log/cups/cups-browsed_log ('file'), to stderr ('stderr'), or
# not at all ('none')?

DebugLogging file
# DebugLogging stderr
# DebugLogging file stderr
# DebugLogging none


# Which protocols will we use to discover printers on the network?
# Can use DNSSD and/or CUPS and/or LDAP, or 'none' for neither.

BrowseRemoteProtocols dnssd cups


# Which protocols will we use to broadcast shared local printers to the network?
# Can use DNSSD and/or CUPS, or 'none' for neither.
# Only CUPS is actually supported, as DNSSD is done by CUPS itself (we ignore
# DNSSD in this directive).

# BrowseLocalProtocols none


# Settings of this directive apply to both BrowseRemoteProtocols and
# BrowseLocalProtocols.
# Can use DNSSD and/or CUPS and/or LDAP, or 'none' for neither.

# BrowseProtocols none


# Only browse remote printers (via DNS-SD or CUPS browsing) from
# selected servers using the "BrowseAllow", "BrowseDeny", and
# "BrowseOrder" directives

# This serves for restricting the choice of printers in print dialogs
# to trusted servers or to reduce the number of listed printers in the
# print dialogs to a more user-friendly amount in large networks with
# very many shared printers.

# This only filters the selection of remote printers for which
# cups-browsed creates local queues. If the print dialog uses other
# mechanisms to list remote printers as for example direct DNS-SD
# access, cups-browsed has no influence. cups-browsed also does not
# prevent the user from manually accessing non-listed printers.

# "BrowseAllow": Accept printers from these hosts or networks. If
# there are only "BrowseAllow" lines and no "BrowseOrder" and/or
# "BrowseDeny" lines, only servers matching at last one "BrowseAllow"
# line are accepted.

# "BrowseDeny": Deny printers from these hosts or networks. If there
# are only "BrowseDeny" lines and no "BrowseOrder" and/or
# "BrowseAllow" lines, all servers NOT matching any of the
# "BrowseDeny" lines are accepted.

# "BrowseOrder": Determine the order in which "BrowseAllow" and
# "BrowseDeny" lines are applied. With "BrowseOrder Deny,Allow" in the
# beginning all servers are accepted, then the "BrowseDeny" lines are
# applied to exclude unwished servers or networks and after that the
# "BrowseAllow" lines to re-include servers or networks. With
# "BrowseOrder Allow,Deny" we start with denying all servers, then
# applying the "BrowseAllow" lines and afterwards the "BrowseDeny"
# lines.

# Default for "BrowseOrder" is "Deny.Allow" if there are both
# "BrowseAllow" and "BrowseDeny" lines.

# If there are no "Browse..." lines at all, all servers are accepted.

# BrowseAllow All
# BrowseAllow cups.example.com
# BrowseAllow 192.168.1.12
# BrowseAllow 192.168.1.0/24
# BrowseAllow 192.168.1.0/255.255.255.0

# BrowseDeny All
# BrowseDeny printserver.example.com
# BrowseDeny 192.168.1.13
# BrowseDeny 192.168.3.0/24
# BrowseDeny 192.168.3.0/255.255.255.0

# BrowseOrder Deny,Allow
# BrowseOrder Allow,Deny


# The interval between browsing/broadcasting cycles, local and/or
# remote, can be adjusted with the BrowseInterval directive.

# BrowseInterval 60


# Browsing-related operations such as adding or removing printer queues
# and broadcasting are each allowed to take up to a given amount of time.
# It can be configured, in seconds, with the BrowseTimeout directive.
# Especially queues discovered by CUPS broadcasts will be removed after
# this timeout if no further broadcast from the server happens.

# BrowseTimeout 300


# Filtering of remote printers by other properties than IP addresses
# of their servers

# Often the desired selection of printers cannot be reached by only
# taking into account the IP addresses of the servers. For these cases
# there is the BrowseFilter 

Bug#909423: cups-browsed: Unusual behaviour with the default CreateIPPPrinterQueues

2018-11-27 Thread Till Kamppeter

So to investigate this further I would need a log file of cups-browsed.

You get a log file if there is a line

DebugLogging file

in cups-browsed.conf

The log file will by default be created as

/var/log/cups/cups-browsed_log

Please attach your log file (from starting cups-browsed until 
observation of wrong behavior) to this bug report. Also attach your 
cups-browsed.conf.


   Till



Bug#909423: cups-browsed: Unusual behaviour with the default CreateIPPPrinterQueues

2018-11-27 Thread Brian Potkin
found 909423 1.21.4-4
thanks


On Mon 26 Nov 2018 at 20:34:10 +, Brian Potkin wrote:

> On Sun 23 Sep 2018 at 14:59:22 +0100, Brian Potkin wrote:
> 
> > Package: cups-browsed
> > Version: 1.21.2-1
> > Severity: minor
> > Tags: upstream
> > 
> > 
> > The default for CreateIPPPrinterQueues is "LocalOnly". All the lines for
> > the directive were commented out and cups-browsed restarted. AN IPP
> > printer on the network appears in the 'lpstat -a' output. A minute later
> > it disappears. A log is attached.
> > 
> > The IPP printer is not displayed at all after restarting cups-browsed
> > with "CreateIPPPrinterQueues LocalOnly" uncommented. Shouldn't the
> > default behave in the same way?
> 
> With cups-browsed 1.21.4-4 we have a change in behaviour. Having all
> lines for "CreateIPPPrinterQueues" commented out gives me what an
> uncommented "CreateIPPPrinterQueues Driverless" would give me. I do
> not mind that, but maybe this is not intended.

This is not observed on another couple of unstable installations or
(after some purging and reinstallation) on the initial installation
used. The original description of the issue stands.

Regards,

Brian.



Bug#909423: cups-browsed: Unusual behaviour with the default CreateIPPPrinterQueues

2018-11-26 Thread Brian Potkin
On Sun 23 Sep 2018 at 14:59:22 +0100, Brian Potkin wrote:

> Package: cups-browsed
> Version: 1.21.2-1
> Severity: minor
> Tags: upstream
> 
> 
> The default for CreateIPPPrinterQueues is "LocalOnly". All the lines for
> the directive were commented out and cups-browsed restarted. AN IPP
> printer on the network appears in the 'lpstat -a' output. A minute later
> it disappears. A log is attached.
> 
> The IPP printer is not displayed at all after restarting cups-browsed
> with "CreateIPPPrinterQueues LocalOnly" uncommented. Shouldn't the
> default behave in the same way?

With cups-browsed 1.21.4-4 we have a change in behaviour. Having all
lines for "CreateIPPPrinterQueues" commented out gives me what an
uncommented "CreateIPPPrinterQueues Driverless" would give me. I do
not mind that, but maybe this is not intended.

Regards,

Brian.



Bug#909423: cups-browsed: Unusual behaviour with the default CreateIPPPrinterQueues

2018-09-23 Thread Brian Potkin
Package: cups-browsed
Version: 1.21.2-1
Severity: minor
Tags: upstream


The default for CreateIPPPrinterQueues is "LocalOnly". All the lines for
the directive were commented out and cups-browsed restarted. AN IPP
printer on the network appears in the 'lpstat -a' output. A minute later
it disappears. A log is attached.

The IPP printer is not displayed at all after restarting cups-browsed
with "CreateIPPPrinterQueues LocalOnly" uncommented. Shouldn't the
default behave in the same way?

Regards,

Brian.




cups-browsed_log.gz
Description: application/gzip