Till Kamppeter [2016-06-27 21:42 -0000]:
> Is the fix of bug 1579905 applied?

I just downloaded xenial's 1.8.3-2ubuntu3 and that has that fix (i. e.
the After=cups.service).

Unrelated note: cups-browsed.service has *both* Wants=cups.service and
Requires=cups.service, so the Wants= is entirely unnecessary as it
gets dominated by Requires=. (But this isn't causing a bug, just a
stylistic issue).

> I think that pitti's approach is also important as cups-browsed needs
> the network. At least on some systems it communicates with CUPS via
> localhost:631 which probably would not work if the network is already
> shut down.

loopback should still be up at that time, this is mostly about the
"real" network.

> cups-browsed needs to communicate with CUPS also during its
> shutdown as it removes the CUPS queues it created when shutting down. So
> it is important that cups-browsed shuts down before CUPS and before the
> network.

Right, but that's bug 1579905. Jane's journal clearly shows that cups
has *not* been stopped yet when stopping cups-browsed, so that's fine.

-- 
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     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to