Comment 4 for bug 1780232

I'm completely surprised that you can reproduce this bug, and I have no idea why :-/ (needless to say, can't reproduce it on my system)

Can you please re-try with the attached version of aa-unconfined, which has some debugging code added? (No need to replace your /usr/sbin/aa-unconfined, just store it whereever you like and run it with "python3 aa-unconfined".)

If you can still reproduce the problem, you'll get one or more lines like

    *** OSError raised for pid 123

Please check for which processes you get these messages, and under which AppArmor profile they are running. (As an alternative, attach all "OSError raised" lines together with the output of "ps Zaux" so that I can have a look at it.)

Please also check "cat /proc/$PID/attr/current" for the listed processes if it shows something unusual.