cups-browsed.service should have 0s stop timeout
Bug #2066079 reported by
Julian Andres Klode
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cups (Ubuntu) |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
cups-browsed can hang at shutdown in a busy network, but there's nothing important that requires it to have an ordered shutdown, so just set the timeout to 0 to kill it immediately.
Revision history for this message
| Till Kamppeter (till-kamppeter) wrote | #1 |
| Changed in cups (Ubuntu): | |
| status: | New → Incomplete |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in cups (Ubuntu): | |
| status: | Incomplete → Expired |
To post a comment you must log in.
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.