zoolook: If you have the same symptoms, these would be two interesting experiments:
* Shut down the network manually (disconnect in NM applet), then stop cups-browsed. Does that work/hang? * Run these in a terminal: sudo mkdir -p /lib/systemd/system/cups-browsed.service.d printf '[Unit]\nAfter=network.target\n' | sudo tee /lib/systemd/system/cups-browsed.service.d/network.conf sudo systemctl daemon-reload sudo systemctl restart cups-browsed This will modify the shutdown order to force browsed to stop before shutting down the network. My hunch is that browsed wants to send something to the network on shutdown, but that is already down, so it times out there. Does shutdown work with that? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1591274 Title: cups-browsed hangs on shutdown Status in cups package in Ubuntu: Incomplete Bug description: I have a new XPS13, running an up-to-date 16.04. The shutdown process takes ages - something is clearly getting stuck. It eventually completes, but is (or seems like) several minutes. Happy to help debug if you can give instructions on how to see what's stuck. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1591274/+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
