Christopher's original report specified a --click explicity; for that, autopkgtest will modify the apparmor profile to allow introspection and loading stuff from the test deps temp dir. But the ubuntu-sanity-tests invocation does not involve any explicit --click, thus there is no apparmor modification.
For this it seems we need to bite the bullet and modify the apparmor profile for *all* installed clicks: i. e. if the test is running in a touch+apparmor+click environment, but only a Debian package is specified and no --click. This will add 3 minutes to the test run (one complete apparmor profile update takes ~ 1.5 min, and we have to revert it at the end of the test), but I guess we have to bite that bullet.
Mystery solved:
[13232.018182] type=1400 audit(142484404 7.097:122) : apparmor="DENIED" operation="open" profile= "com.ubuntu. camera_ camera_ 3.0.0.484" name="/ tmp/adt- run.cXxSBr/ deps/usr/ lib/libqttestab ility.so. 1.0.0" pid=31948 comm="camera-app" requested_mask="r" denied_mask="r" fsuid=32011 ouid=0
Christopher's original report specified a --click explicity; for that, autopkgtest will modify the apparmor profile to allow introspection and loading stuff from the test deps temp dir. But the ubuntu-sanity-tests invocation does not involve any explicit --click, thus there is no apparmor modification.
For this it seems we need to bite the bullet and modify the apparmor profile for *all* installed clicks: i. e. if the test is running in a touch+apparmor+ click environment, but only a Debian package is specified and no --click. This will add 3 minutes to the test run (one complete apparmor profile update takes ~ 1.5 min, and we have to revert it at the end of the test), but I guess we have to bite that bullet.