This bug was fixed in the package snap-confine - 1.0.38-0ubuntu0.16.04.10
--------------- snap-confine (1.0.38-0ubuntu0.16.04.10) xenial; urgency=medium
* debian/usr.lib.snapd.snap-confine: - synchronize apparmor profile with upstream 1.0.40 release. (LP: #1597842, LP: #1615113, LP: #1584456)
snap-confine (1.0.38-0ubuntu0.16.04.9) xenial; urgency=medium
* debian/patches/04_not_die_unknown_locations.patch: - move to /var/lib/snapd/void (with mode 0) if the current location cannot be preserved (LP: #1612684)
-- Zygmunt Krynicki <email address hidden> Wed, 24 Aug 2016 20:31:12 +0200
This bug was fixed in the package snap-confine - 1.0.38- 0ubuntu0. 16.04.10
--------------- 0ubuntu0. 16.04.10) xenial; urgency=medium
snap-confine (1.0.38-
* debian/ usr.lib. snapd.snap- confine:
- synchronize apparmor profile with upstream 1.0.40 release.
(LP: #1597842, LP: #1615113, LP: #1584456)
snap-confine (1.0.38- 0ubuntu0. 16.04.9) xenial; urgency=medium
* debian/ patches/ 04_not_ die_unknown_ locations. patch:
- move to /var/lib/snapd/void (with mode 0) if the current
location cannot be preserved (LP: #1612684)
-- Zygmunt Krynicki <email address hidden> Wed, 24 Aug 2016 20:31:12 +0200