[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#905764: cups-browsed: restarting always generates log message "Error creating cups notify handler: Could not connect: No such file or directory"



Package: cups-browsed
Version: 1.20.4-1
Severity: minor

This is basically a fresh install of stable. Every day, after the cups
logrotate where cups is restarted, cups-browsed is also restarted by
systemd. Upon stopping, cups-browsed generates this log message:

cups-browsed[7468]: Error creating cups notify handler: Could not connect: No such file or directory

This happened with the stable 1.11.6-3 version, and also with 1.20.4-1
which I tried to see if the problem might have been solved in the
meantime.

I find it strange that the message only comes when cups-browsed is
stopped.

I probably don't need cups-browsed in my environment, so I might as well
deinstall it, but IMHO it shouldn't be generating such messages without
any indication how to fix it.

Seeing that avahi-daemon is recommended, I tried installing that and
that fixed it. However as it's not a hard dependency, cups-browsed
should function without avahi-daemon installed.


Thanks,
Paul


-- System Information:
Debian Release: 9.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-6-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cups-browsed depends on:
ii  cups-daemon       2.2.1-8+deb9u1
ii  libavahi-client3  0.6.32-2
ii  libavahi-common3  0.6.32-2
ii  libavahi-glib1    0.6.32-2
ii  libc6             2.24-11+deb9u3
ii  libcups2          2.2.1-8+deb9u1
ii  libcupsfilters1   1.20.4-1
ii  libglib2.0-0      2.50.3-2
ii  libldap-2.4-2     2.4.44+dfsg-5+deb9u1
ii  lsb-base          9.20161125

Versions of packages cups-browsed recommends:
pn  avahi-daemon  <none>

cups-browsed suggests no packages.

-- no debconf information


Reply to: