I’ve just installed the Beta1 of Ubuntu Budgie and subsequently did a apt update && apt dist-upgrade before doing anything else.
After installing some snaps, I am seeing that they don’t have access to the network:
[ 1715.982033] audit: type=1400 audit(1504442601.131:69): apparmor="DENIED" operation="open" profile="snap.corebird.corebird" name="/run/systemd/resolve/stub-resolv.conf" pid=9894 comm="curl" requested_mask="r" denied_mask="r" fsuid=1000 ouid=102
[ 1724.211489] audit: type=1107 audit(1504442609.362:70): pid=801 uid=105 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/NetworkManager" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.11" pid=9880 label="snap.corebird.corebird" peer_pid=868 peer_label="unconfined"
[ 1724.212990] audit: type=1400 audit(1504442609.364:71): apparmor="DENIED" operation="open" profile="snap.corebird.corebird" name="/run/systemd/resolve/stub-resolv.conf" pid=9880 comm="pool" requested_mask="r" denied_mask="r" fsuid=1000 ouid=102
[ 1724.213328] audit: type=1400 audit(1504442609.364:72): apparmor="DENIED" operation="open" profile="snap.corebird.corebird" name="/run/systemd/resolve/stub-resolv.conf" pid=9880 comm="pool" requested_mask="r" denied_mask="r" fsuid=1000 ouid=102
This is not the only snap
For which I think this might be the cause for (just guessing by information I recalled was posted on posted on Ubuntu Foundations Development Summary – August 30, 2017:
The resolvconf and ifupdown packages have been dropped from the base debootstrap set in artful; new installs of 17.10 will now exclusively use systemd-resolved instead of resolvconf, and NetworkManager/systemd-networkd instead of ifupdown. For background on these changes, see http://blog.cyphermox.net/2017/06/netplan-by-default-in-1710.html
Here’s my system information (take notice that I am using an Ubuntu kernel):
$ snap info --version
snap 2.27.5+17.10
snapd 2.27.5+17.10
series 16
ubuntu 17.10
kernel 4.12.0-12-generic
$ uname -a
Linux mirkwood 4.12.0-12-generic #13-Ubuntu SMP Thu Aug 17 16:13:25 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
And that in the case of this snap, everything seems to be setup as snapd expects it to be:
$ snap change 4
Status Spawn Ready Summary
Done 2017-09-02T23:38:42Z 2017-09-03T00:04:54Z Download snap "corebird" (40) from channel "stable"
Done 2017-09-02T23:38:42Z 2017-09-03T00:04:57Z Fetch and check assertions for snap "corebird" (40)
Done 2017-09-02T23:38:42Z 2017-09-03T00:04:57Z Mount snap "corebird" (40)
Done 2017-09-02T23:38:42Z 2017-09-03T00:04:57Z Copy snap "corebird" data
Done 2017-09-02T23:38:42Z 2017-09-03T00:04:58Z Setup snap "corebird" (40) security profiles
Done 2017-09-02T23:38:42Z 2017-09-03T00:04:58Z Make snap "corebird" (40) available to the system
Done 2017-09-02T23:38:42Z 2017-09-03T00:04:58Z Set automatic aliases for snap "corebird"
Done 2017-09-02T23:38:42Z 2017-09-03T00:04:58Z Setup snap "corebird" aliases
Done 2017-09-02T23:38:42Z 2017-09-03T00:04:58Z Run install hook of "corebird" snap if present
Done 2017-09-02T23:38:42Z 2017-09-03T00:04:58Z Start snap "corebird" (40) services
Done 2017-09-02T23:38:42Z 2017-09-03T00:04:58Z Run configure hook of "corebird" snap if present
So with all this information, I’ve got it all working again by:
sudo apt install resolvconf
And everything is working again.
This should however be taken into account for new installs and work with the announced mechanisms new installs will have.
PS: new installs, don’t forget to sudo apt install snapd-xdg-open 
