Comment # 1 on bug 1120472 from Christian Boltz

That's interesting[tm], and it looks like openQA found a scenario that I
thought would never happen. (Actually I wasn't even aware that we have AppArmor
tests in openQA ;-) - thanks to whoever added them!)

I just tried to reproduce the issue locally by doing what openQA does, but
(un)fortunately aa-logprof "just works" as expected.

I have two questions:

Is there a way to get the debug log /tmp/apparmor-bugreport-*.txt from openQA?
(note that the filename is mktemp-generated)
The debug log contains the content of variables etc. and is hopefully helpful
to find out what happens.

Also, where can I find the source code of the AppArmor tests done by openQA?
Maybe there's a detail I missed in the screenshot.