There is a known bug tat 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.
** Changed in: cups (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066079
Title:
cups-browsed.service should have 0s stop timeout
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2066079/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
