Comment 1 for bug 2066079

There is a known bug that cups-browsed can be stuck in a busy loop, bug 2018504. Most probably it is stuck for you and so does not handle the SIGTERM to shut down.

Usually cups-browsed's shutdown removes the local print queues which cups-browsed has created and therefore we should not eliminate it by doing a SIGKILL right away.

So before setting the timeout to 0 I would like you to check whether your cups-browsed is stuck and if not, do further checks to investigate whether shutdown takes too long.