Package: cups-browsed
Version: 1.20.1-1+b1
Severity: normal
Here's a sample session:
# ps auxw|grep cups
root 27143 0.0 0.1 19508 9600 ? Ss Apr04 0:07
/usr/sbin/cupsd -l
root 27144 0.0 0.1 42080 11184 ? Ssl Apr04 0:00
/usr/sbin/cups-browsed
root 31856 0.0 0.0 5284 876 pts/5 RN+ 14:27 0:00 grep cups
~-0# /etc/init.d/cups stop;/etc/init.d/cups start
[ ok ] Stopping cups (via systemctl): cups.service.
[ ok ] Starting cups (via systemctl): cups.service.
~-0# ps auxw|grep cups
root 31935 0.0 0.0 17516 6932 ? Ss 14:28 0:00
/usr/sbin/cupsd -l
root 31954 0.0 0.0 5284 796 pts/5 SN+ 14:28 0:00 grep cups
~-0#
As you can see before the `cups stop; cups start` both `cupsd` and `cups-
browsed` were running, whereas afterwards only `cupsd` is running.
I believe this behavior is incorrect since no part of `cups stop; cups start`
says explicitly that we want `cups-browsed` to be stopped. So either `cups
stop` should not stop `cups-browsed`, or it should check if `cups-browsed` is
running and arrange to make sure a subsequent `cups start` restarts it if
applicable.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 4.14.0-3-686-pae (SMP w/2 CPU cores)
Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages cups-browsed depends on:
ii cups-daemon 2.2.7-1
ii libavahi-client3 0.7-3.1
ii libavahi-common3 0.7-3.1
ii libavahi-glib1 0.7-3.1
ii libc6 2.27-3
ii libcups2 2.2.7-1
ii libcupsfilters1 1.20.1-1+b1
ii libglib2.0-0 2.56.0-4
ii libldap-2.4-2 2.4.45+dfsg-1
ii lsb-base 9.20170808
Versions of packages cups-browsed recommends:
ii avahi-daemon 0.7-3.1
cups-browsed suggests no packages.
-- no debconf information
