* New upstream release, LP: #1786438
- packaging/fedora: Merge changes from Fedora Dist-Git
- snapcraft: do not use --diry in mkversion.sh
- cmd: add systemd environment generator
- snap-confine: map /var/lib/extrausers into snaps mount-namespace
- tests: cherry-pick test fixes from master for 2.35
- systemd: do not run "snapd.snap-repair.service.in on firstboot
bootstrap
- interfaces: retain order of inserted security backends
- selftest: detect if apparmor is unusable and error
http:// cloud-images. ubuntu. com/cosmic/ 20180906/ unpacked/ cosmic- daily.changelog outlines the changed packages between the two images. I strongly suspect that the root cause of this is the systemd environment generator added in the latest version of snapd, so I've added snapd to this bug.
The changelog for the latest snapd version:
snapd (2.35.1+18.10) cosmic; urgency=medium
* New upstream release, LP: #1786438 snap-repair. service. in on firstboot
- packaging/fedora: Merge changes from Fedora Dist-Git
- snapcraft: do not use --diry in mkversion.sh
- cmd: add systemd environment generator
- snap-confine: map /var/lib/extrausers into snaps mount-namespace
- tests: cherry-pick test fixes from master for 2.35
- systemd: do not run "snapd.
bootstrap
- interfaces: retain order of inserted security backends
- selftest: detect if apparmor is unusable and error
-- Michael Vogt <email address hidden> Mon, 03 Sep 2018 14:44:06 +0200