Bug#759348: cups-browsed: cups-browsed may hang during restart if CUPS is socket-triggered

[Brian Potkin <claremont102@gmail.com>]

retitle bugnumber cups-browsed may hang during restart if CUPS is socket-triggered
thanks


On Thu 30 Oct 2014 at 18:48:36 +0000, Brian Potkin wrote:

> I'm away from home at present but will be able to test and do as you
> suggest on this Saturday/Sunday.

The unstable install I started with had cups 1.7.5-4 and version 1.0.61-2
of cups-browsed. Retesting with the command

   systemctl stop cups cups-browsed

results in (as before) cups-browsed entering a failed state,

Updating and then a dist-update gets cups 1.7.5-7. No reboot.

The command above completes immediately and journalctl shows both cups
and cups-browsed services as inactive. I can confirm that the unwanted
behaviour has disappeared.

  root@jessie-b2:~# systemctl stop cups cups-browsed.service
  Warning: Stopping cups.service, but it can still be activated by:
    cups.path
    cups.socket

  root@jessie-b2:~# systemctl status cups cups-browsed.service
•   cups.service - CUPS Printing Service
     Loaded: loaded (/lib/systemd/system/cups.service; enabled)
     Active: inactive (dead) since Sat 2014-11-01 20:32:01 GMT; 4s ago
       Docs: man:cupsd(8)
             man:cupsd.conf(5)
    Process: 4177 ExecStart=/usr/sbin/cupsd -f (code=exited, status=0/SUCCESS)
   Main PID: 4177 (code=exited, status=0/SUCCESS)

•   cups-browsed.service - Make remote CUPS printers available locally
     Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled)
     Active: inactive (dead) since Sat 2014-11-01 20:32:01 GMT; 4s ago
    Process: 4178 ExecStart=/usr/sbin/cups-browsed (code=exited, status=0/SUCCESS)
   Main PID: 4178 (code=exited, status=0/SUCCESS)


Regards,

Brian.