Some more hints: cups-browsed uses avahi-daemon for printer discovery. It does not matter whether avahi-daemon shuts down before or after cups-browsed. If avahi- daemon shuts down first, cups-browsed removes its queues triggered by them going away from DNS-SD, if cups-browsed shuts down first, it removes the queues due to its own shutdown.
cups-browsed uses D-Bus to communicate with avahi-daemon (avahi-daemon informs about devices in the network appearing and going away) and with cupsd (cupsd reports activity on the print queues via D-Bus). cups-browsed also communicates with cupsd or cups-browsed on remote machines via the regular network (no loopback) when the legacy CUPS protocol for printer browsing and/or broadcasting is used (in cups- browsed.conf at least one of "BrowseProtocols", "BrowseRemoteProtocols", and "BrowseLocalProtocols" has "cups" set. So for me it seems that both regular network and D-Bus must be up and running while cups-browsed is running and cups-browsed has to shut down before these two (and to start after these two). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1591274 Title: cups-browsed hangs on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1591274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
