On Wed, Nov 11, 2009 at 09:28:43AM -0000, nZain wrote:
> I rebooted, since I didn't know, how to reload apparmor.
Okay, that will have update the policy in the kernel as well.
> I didn't modify /etc/apparmor.d/usr.bin.evince - maybe this file
> overrides the other one?
Nope, that's fine if you modified /etc/apparmor.d/abstractions/evince;
it gets pulled into the policies defined in
/etc/apparmor.d/usr.bin.evince.
Can you attach your modified version of
/etc/apparmor.d/abstractions/evince to the bug report? I'm quite
confused as to why adding '/usr/bin/totem ixr,' results in an apparmor
rejection that's preventing /ubr/bin/totem from executing (the '::x' bit
listed in your kern.log). Can you also verify that the rejections that
are showing up in kern.log are the same?
On Wed, Nov 11, 2009 at 09:28:43AM -0000, nZain wrote:
> I rebooted, since I didn't know, how to reload apparmor.
Okay, that will have update the policy in the kernel as well.
> I didn't modify /etc/apparmor. d/usr.bin. evince - maybe this file
> overrides the other one?
Nope, that's fine if you modified /etc/apparmor. d/abstractions/ evince; d/usr.bin. evince.
it gets pulled into the policies defined in
/etc/apparmor.
Can you attach your modified version of d/abstractions/ evince to the bug report? I'm quite
/etc/apparmor.
confused as to why adding '/usr/bin/totem ixr,' results in an apparmor
rejection that's preventing /ubr/bin/totem from executing (the '::x' bit
listed in your kern.log). Can you also verify that the rejections that
are showing up in kern.log are the same?
Thanks for your patience in troubleshooting this!
-- NxNW.org/ ~steve/
Steve Beattie
<email address hidden>
http://