Package: cups-browsed
Version: 1.0.34-2
Severity: normal

when using the cups 1.6 mdns discovery in a setup where a server
announces itself as "servername.local", a client's cups browser can find
the server, but upon printing, gtk applications get stuck at the
"getting printer information" stage (the printer is shown, but it can
not be printed to due to disabled print button).

network traffic analysis showed that the client repeatedly tried to look
up "servername.local" using traditional dns, which of course failed.

installing libnss-mdns solved the problem; i therefore ask you to depend
or at least recommend libnss-mdns from cups-browsed. given the browser
discovers hosts based on mdns and passes their host names on to cups
(which later one way or another will have to resolve them), i think a
"depends" is justified, but a "recommends" probably can be argued for
too.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.8-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages cups-browsed depends on:
ii  cups              1.6.2-8
ii  libavahi-client3  0.6.31-2
ii  libavahi-common3  0.6.31-2
ii  libavahi-glib1    0.6.31-2
ii  libc6             2.17-4
ii  libcups2          1.6.2-8
ii  libglib2.0-0      2.36.1-2build1

cups-browsed recommends no packages.

cups-browsed suggests no packages.

-- no debconf information

-- 
To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom

Attachment: signature.asc
Description: Digital signature

Reply via email to