Public bug reported:
If the user tries cancels out of a Snap installation job with Ctrl+C,
the job will continue in the background. Snap provides the user with an
option to abort a Snap job ('snap abort <id>'), but running the command
doesn't seem to do anything until the current job is finished.
Ubuntu version: Ubuntu MATE 16.04
Snapd version: 2.0.8
To recreate:
1. Run a Snap job with `snap install <package>`. hello-world works well.
2. Close snap with Ctrl+C. You'll be returned to Bash, but the system monitor
reports that network activity is still running. Checking the job status with
`snap change <id>` will show that the current job status is "doing".
3. Run `snap abort <id>`.
Expected result: The Snap job will halt and there will be no network usage.
Actual result: The Snap job will be listed as "Abort", and all subsequent jobs
will be listed as "Hold" until the current job (usually a big download) is
finished. Network will still be used, and Snap will not properly halt the job
until the kernel kills the daemon at shutdown. New Snap jobs cannot be started
until the current job is finished.
** Affects: snap (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1593439
Title:
Aborting a Snap job does nothing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snap/+bug/1593439/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
