forked, background processes can prevent "snap remove" with unhelpful message

[Chad Miller]

Imagine a snapped program forking off a child to do work and before it exits, the user asks to remove the package.

snapd could "lsof" to find processes beneath the mounted snap package and kill it after a Y/N prompt.

Right now, it complains that the zucchini is quite busy. Or maybe something about squashes. That implementation detail shouldn't be exposed to users.

[Seth Arnold (seth-arnold)]

Perhaps cgroups or systemd sessions would be more reliable than lsof: https://github.com/systemd/systemd/blob/master/NEWS#L29

[Michael Vogt (mvo)]

This is fixed now, we do lazy umount which prevents this kind of error.