Bug#792730: cups-client: cups clients don't connect to the correct socket

[Yves-Alexis Perez <corsac@debian.org>]

Package: cups-client
Version: 2.0.3-8
Severity: normal

Hi,

I'm using CUPS daemon using socket only configuration (Listen
/var/run/cups/cups.sock in cupsd.conf and
/etc/systemd/system/sockets.target.wants/cups.socket ->
/lib/systemd/system/cups.socket).

Socket activation works fine, but since some time (I don't print much so
I'm unsure when), client (system-config-printer, chromium, libreoffice
etc.) can't connect to the socket.

Actually, strace shows only a stat() on the cups.sock, then a connect()
to [::1]:631

Adding a /etc/cups/client.conf with:

ServerName /var/run/cups/cups.sock                                              

workarounds the issue, but it was working just fine before.

Regards,
-- 
Yves-Alexis


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (450, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cups-client depends on:
ii  adduser        3.113+nmu3
ii  cups-common    2.0.3-8
ii  libc6          2.19-19
ii  libcups2       2.0.3-8
ii  libcupsimage2  2.0.3-8

cups-client recommends no packages.

Versions of packages cups-client suggests:
ii  cups       2.0.3-8
pn  cups-bsd   <none>
ii  smbclient  2:4.1.17+dfsg-4
pn  xpp        <none>

-- no debconf information