snapd can't be purged with latest AWS Xenial AMI
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
Invalid
|
Undecided
|
Unassigned | ||
snapd |
Fix Released
|
Medium
|
Unassigned |
Bug Description
The latest AMI for Xenial with the AMI name listed below fails when running apt-get purge snapd:
ubuntu/
I have confirmed the command works as expected on the following AMI and older:
ubuntu/
I have listed the output of the command below:
/home/ubuntu# apt-get purge snapd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
snapd* ubuntu-
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
After this operation, 94.8 MB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 51356 files and directories currently installed.)
Removing ubuntu-
Removing snapd (2.37.4ubuntu0.1) ...
Purging configuration files for snapd (2.37.4ubuntu0.1) ...
Stopping snap.amazon-
Stopping unit snap.amazon-
Waiting until unit snap.amazon-
snap.amazon-
Removing snap.amazon-
Stopping snap-amazon\
Stopping unit snap-amazon\
Waiting until unit snap-amazon\
snap-amazon\
Removing snap amazon-ssm-agent and revision 1068
Removing snap-amazon\
Stopping snap-core-
Stopping unit snap-core-
Waiting until unit snap-core-
snap-core-
Removing snap core and revision 6673
Removing snap-core-
Final directory cleanup
Discarding preserved snap namespaces
Removing extra snap-confine apparmor rules
Removing snapd cache
rm: cannot remove '/var/cache/
dpkg: error processing package snapd (--purge):
subprocess installed post-removal script returned error exit status 1
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for mime-support (3.59ubuntu1) ...
Errors were encountered while processing:
snapd
E: Sub-process /usr/bin/dpkg returned an error code (1)
Changed in snapd: | |
milestone: | none → 2.38 |
Thanks for the bugreport. This is fixed in xenial-proposed with snapd 2.38