Hello, Am Sonntag, 21. Januar 2018, 15:39:11 CET schrieb Lakshmipathi.G:
IIRC systemctl stop apparmor does not work anymore as expected (see Christian's message below).
Spot on! openqa-gru got re-started after using 'sudo aa-teardown' :-)
And now, please check your /var/log/audit/audit.log or run aa-logprof to find out what needs to be added to the profile, and open a bugreport ;-) BTW: Instead of unloading all profiles with aa-teardown, it's usually better to switch the profile to complain (learning) mode with aa-complain /etc/apparmor.d/usr.bin.openqa-gru (adjust the profile filename, the above is only a guess!) because that gives you a more complete log of things that need to be added to the profile. Regards, Christian Boltz -- I believe the technical term is "Oops!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org