It seems that AppArmor may activate during kernel (linux-image) update
because it is one of dependencies.

Dňa 11. 9. 2019 o 9:18 Philipp Pilhofer napísal(a):
> Am 02.01.19 um 09:39 schrieb Carsten Schoenert:
>>> The only things I don't understand, how was AppArmor enabled, and how 
>>> was it working for years until the last update of kernel/TB/whatever; I 
>>> have symlinked home dir for long time now... Could be that only the last 
>>> TB update enabled it?
>> very very unlikely. We are in the middle of an ESR release and thus the
>> packaging typically itself isn't changing much.
>> The code responsible for this wasn't touched for over year now. But we
>> won't get new information on this what really did happen on your system.
>> Only if it is reproducible we would see if and were something is maybe
>> broken and not correctly working.
> After updating from stretch to buster, I did have exactly that problem. After 
> longer testing I found
> it's apparmor. I never used apparmor at all or activated anything, so I don't 
> know how this happened.
> Switching off the profile as described here 
> ( made it
> work again. Is this the way to go or is there anything else I have to take 
> care of?
> Thank you very much,
> Philipp

Reply via email to