Note that there is also another cause for cups-browsed hanging on shutdown, which can also occur with the fix for this bug applied. It is reported to Debian here
It happens when CUPS is only listening on the domain socket and not on localhost:631 as cups-browsed then principally uses the domain socket in this case but at some points, especially during procedures of the shutdown, it uses localhost:631.
I have already fixed this problem and will issue cups-filters 1.11.3 with the fix soon and put it into Debian and Yakkety.
So if your cups-browsed still hangs, DO NOT re-open this bug, please report a new bug referring to the Debian bug here on Launchpad so that we can conduct another SRU there.
Note that there is also another cause for cups-browsed hanging on shutdown, which can also occur with the fix for this bug applied. It is reported to Debian here
https:/ /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 832637
It happens when CUPS is only listening on the domain socket and not on localhost:631 as cups-browsed then principally uses the domain socket in this case but at some points, especially during procedures of the shutdown, it uses localhost:631.
I have already fixed this problem and will issue cups-filters 1.11.3 with the fix soon and put it into Debian and Yakkety.
So if your cups-browsed still hangs, DO NOT re-open this bug, please report a new bug referring to the Debian bug here on Launchpad so that we can conduct another SRU there.