https://bugzilla.novell.com/show_bug.cgi?id=850058 https://bugzilla.novell.com/show_bug.cgi?id=850058#c5 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |suse-beta@cboltz.de Resolution|FIXED | --- Comment #5 from Christian Boltz <suse-beta@cboltz.de> 2013-11-23 22:44:40 CET --- It's nice to find out someone adds a release notes entry without asking the affected packager ;-) In general I agree with the text, but I'd like to add some details to make it more helpful. (In reply to comment #1)
<title>AppArmor and Permission Settings</title> <para> AppArmor is enabled by default. This means more security, but prevent services from working, if you run them in less expected
_might_ prevent services ...
ways. If you encounter strange permission problems, try to disable AppArmor for the affected service.
... try to switch the AppArmor profile for the affected service to complain mode with "aa-complain /usr/bin/$your_service". Complain mode means: allow everything, and log things that the profile would not allow.
Even if it helps report it as a bug, because we want to fix AppArmor profiles to cover also corner cases.
I fully agree with this sentence ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.