Permission Denied and AppArmor Denial

robert_joslyn at selinc.com robert_joslyn at selinc.com
Tue Oct 27 15:46:14 UTC 2015


> Like Seth said, the apparmor denial doesn't have anything to do with 
your
> program-- it is a problem with the launcher's profile. This was fixed in 
LP:
> #1471862, but it appears the change was dropped. I'll catch up with the 
snappy
> core team and see what happened and get that fixed.

Marking my script executable fixed the issue, thanks! I knew it had to be 
something simple. It would be nice if the launcher could provide some 
useful output, as you state in that bug.

In reading over the documentation again, the initial tutorial [1] does 
show setting the binary as executable, but the "Snapcraft: Advanced 
features" page [2] says this in reference to the binaries section of the 
snapcraft.yaml, "The above will take care of making the script executable, 
adding it to the user's path and install it in the right place." This 
wording should be changed if Snapcraft is not actually marking the binary 
as executable. Alternatively, it would be nice if Snapcraft did this 
automatically as stated, or maybe displayed a warning about non-executable 
binaries.

[1] - https://developer.ubuntu.com/en/snappy/build-apps/your-first-snap/
[2] - 
https://developer.ubuntu.com/en/snappy/build-apps/snapcraft-advanced-features/


Thanks,

--
Robert Joslyn
Software Engineer, R&D - Automation
Schweitzer Engineering Laboratories
509-332-1890 ext. 3214



More information about the snappy-app-devel mailing list