This symptom is fixed in the current master code (and likely in the
latest SRU that is going in now). The umount will happen synchronously
even if there are still processes alive.
That said, please note that the old behavior was not as bad as it sounds
from the description. The snapd daemon is not stuck due to the original
removal being stopped, and CTRL-C will correctly not force it to simply
abort midway through. Instead, snapd will keep track of the pending work
and retry every few minutes by itself, attempting to complete the work
that was requested and partially done.
** Changed in: snapd (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592088
Title:
snap command doesn't finish when snapd already gave up
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1592088/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
