Ironically, the reason your CTRL-C + retry did not work is precisely because it _is_ robust.
snapd was busy attempting to remove the existing snap for some reason, and it could not because something in the middle of the process was still using the old snap files. Once these files stopped being used, snapd would finish the removal. You can see the status quo via "snap changes foo", and then more details via "snap change <id>" for the in-progress change. We need to improve the experience so that it's more clear what is going on, and make the behavior reflect what users would expect, but snapd should continue to refuse operations to be done while something conflicting is in progress, and it should continue to not let the system in a bad state just because CTRL-C was used. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585806 Title: snap remove while in /snap/foo/current/... not robust To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1585806/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
