touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #56263
[Bug 1422744] Re: Policy doesn't update when installing Snappy app with same version
yeah, I didn't change snap revision.
Thank you for fast answer and clear explanation.
There is no reason to make it private. I've changed it to public. Most probably, I've incidentally click somewhere on page, sorry for that.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to click-apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1422744
Title:
Policy doesn't update when installing Snappy app with same version
Status in click-apparmor package in Ubuntu:
Won't Fix
Bug description:
I tried to build snap package for Ubuntu Snappy build for Beagle Bone
Black. I make this package for IoT device, it contains AllJoyn (
https://allseenalliance.org/developers/learn ), it require lots of
dbus features. That's why I have to write my own apparmor profile.
After first attempt I've got this message:
[ 499.786552] audit: type=1400 audit(1421754939.200:22): apparmor="DENIED" operation="bind" profile="my-app_my-app-service_1.0.0" pid=1453 comm="alljoyn-daemon" family="unix" sock_type="stream" protocol=0 requested_mask="bind" denied_mask="bind" addr="@alljoyn"
Then I've added line to profile:
unix (create,bind,listen,send,receive,setopt,connect) type=stream,
rebuild the snap, call 'snappy-remote install', but this message still
appears. I even removed profile file in /var/lib/apparmor/profiles dir
(that line was in file) and reboot board, but this message still
appears.
Only after complete snap removal(snappy uninstall) and clean install
this message disappear.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1422744/+subscriptions