ubuntu-core-launcher apparmor denial when creating /tmp/snaps

Bug #1460517 reported by Michael Nelson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snap-confine
Fix Released
Undecided
Unassigned
15.04
Fix Released
Undecided
Unassigned

Bug Description

...or "/tmp/snaps not writeable after installing webdm"

NOTE: Not sure if this is specific to webdm or when snappy installs any 'framework' before /tmp/snaps is created.

Steps to reproduce:
 1) 'sudo snappy install webdm' on a fresh snappy unit
 2) 'ls -al /tmp/snaps' - root only write perms
 3) 'sudo snappy install hello-world'
 4) 'hello-world.echo'

Expected result: "Hello World!"
Actual result: mkdir: cannot create directory ‘/tmp/snaps/hello-world.canonical’: Permission denied

Example: http://paste.ubuntu.com/11489267/

If hello-world is installed first (and so creates /tmp/snaps with ubuntu:ubuntu) then there's no issue: http://paste.ubuntu.com/11489189/

I found a reference to the issue on the mailing list, but didn't see an existing bug report although experienced the same issue today: https://lists.ubuntu.com/archives/snappy-devel/2015-May/000709.html

Related branches

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

This is because the launcher has this in its policy:
    /tmp/snap.*/ w,

It should have this instead:
    /tmp/snap{s,.*}/ w,

affects: webdm → ubuntu-core-launcher
summary: - Cannot run other snaps after first installing webdm
+ ubuntu-core-launcher apparmor denial when creating /tmp/snaps
no longer affects: snappy
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

This was fixed long ago and since then, the implementation changed. Marking Fix Released.

Changed in snap-confine:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.