Desktop example ubuntu-clock-app is broken

It looks like you are plugging the unity7 interface (good). Interfaces weren't autoconnecting until snapd 1.9.2 which was just uploaded today. I tested the clock app just now and this denial is gone, though there are other denials.

Marking as fixed since the other issues are due to packaging.

kernel: [67239.454656] audit: type=1400 audit(1460648529.359:3105): apparmor="DENIED" operation="chmod" profile="snap.ubuntu-clock-app.clock" name="/var/cache/fontconfig/" pid=18439 comm="qmlscene" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0
kernel: [67239.463592] audit: type=1400 audit(1460648529.367:3106): apparmor="DENIED" operation="chmod" profile="snap.ubuntu-clock-app.clock" name="/var/cache/fontconfig/" pid=18439 comm="qmlscene" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0
kernel: [67239.672804] audit: type=1400 audit(1460648529.575:3107): apparmor="DENIED" operation="chmod" profile="snap.ubuntu-clock-app.clock" name="/var/cache/fontconfig/" pid=18439 comm="qmlscene" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0
kernel: [67239.849176] audit: type=1400 audit(1460648529.751:3108): apparmor="DENIED" operation="chmod" profile="snap.ubuntu-clock-app.clock" name="/var/cache/fontconfig/" pid=18439 comm="qmlscene" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0
kernel: [67239.935214] audit: type=1400 audit(1460648529.839:3109): apparmor="DENIED" operation="open" profile="snap.ubuntu-clock-app.clock" name="/usr/share/glib-2.0/schemas/gschemas.compiled" pid=18439 comm="qmlscene" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

Apr 14 18:06:27 daydream kernel: [27379.159879] audit: type=1400 audit(1460649987.640:96): apparmor="DENIED" operation="connect" profile="snap.ubuntu-clock-app.clock" pid=1177 comm="qmlscene" family="unix" sock_type="stream" protocol=0 requested_mask="send receive connect" denied_mask="send connect" addr=none peer_addr="@/tmp/.X11-unix/X0" peer="unconfined"

Daniel, you listed the X denial again. Do you have snapd 1.9.2 installed? You might have to remove the snap and install it again to regenerate the policy.

Jamie, could you expand on what you meant with the other issues being due to packaging? Thanks!

@David, apps need to only use things in the snap-specific data directories, but this is using /var/cache/fontconfig, schema files in /usr and themes in /usr. These are not a result of x11/unity7 not connecting and therefore not this bug.

Hi David,

I set up the Jenkins snap with a custom fontconfig, which may be useful:

https://github.com/evandandrea/jenkins-snap/commit/6afbe244bdd0f9c31ccffa8d0b4ad0947c3c71fc

It doesn't set up the font cache, but that wouldn't be a difficult extension.