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. ** Bug watch added: Debian Bug tracker #832637 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832637 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1579905 Title: cups-browsed causes shutdown hang/delay in Ubuntu 16.04 Status in cups-filters package in Ubuntu: Fix Released Status in cups-filters source package in Xenial: Fix Released Bug description: [SRU justification] When the system is shut down CUPS and cups-browsed are not shut down in a determined order, but cups-browsed needs CUPS still running to perform its shutdown, for removing the print queues it has generated and for saving information about these queues for use in the next session. With CUPS already shut down cups-browsed simply hangs and gets killed after a certain timeout. This can be fixed by defining the correct relationships in the systemd .service files and so the annoying hang can be avoided. [Test case] To reproduce the bug run sudo systemctl stop cups and after some seconds sudo systemctl stop cups-browsed with the shutdown of cups-browsed hanging. On system shutdown one gets the hang, but not always as it can happen that on some shutdowns cups-browsed shuts down before cups. After installing the fixed package, hhutting down cups requires shutting down cups-browsed before, so that the shutdown of cups triggers the shutdown of cups-browsed, making all shutdowns having the two services shut down in the right order avoiding a hang. [Regression potential] None. We only define a dependency between two services to make them shit down in the correct order. [Original report] Using the debug process found here https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917 I have determined that the cause of my 16.04 install's shutdown hang is cups- browsed. It was the only process running when I did a systemctl list- jobs in the VT9 shell. If I do sudo service cups-browsed stop and then shutdown, I do not get a hang. I have confirmed this on a virtual machine and a real system. If I disable cups-browsed from ever starting, my problem is fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1579905/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
