Comment # 13 on bug 1195463 from Noel Power

(In reply to Noel Power from comment #12)
> (In reply to Christian Boltz from comment #11)
[...]
> 
> Thanks for pointing out the important information to save, I will keep an
> eye out, hopefully I will experience this again soon so I remember this bug
> and/or the instructions :-)

Hi Christian, I reproduced this, better still I think I can keep on reproducing
it thanks to a vm (snapshotted before/after)

this is Leap 15.4 (not probably fully updated) but I attempted to update with
https://build.opensuse.org/package/show/home:npower:branches:security:apparmor/apparmor
(adjusts apparmor with /proc/{pipd}/fd rule)

What is happening is the cached file /etc/apparmor.d/cache.d/*/samba-bgqd 
doesn't appear to be updated correctly with the install

on system

localhost:~ # ls -lrt /etc/apparmor.d/cache.d/d29c4283.0/samba-bgqd
-rw------- 1 root root 37305 Mar 23 20:43
/etc/apparmor.d/cache.d/d29c4283.0/samba-bgqd
localhost:~ # ls -lrt /usr/share/apparmor/cache/d29c4283.0/samba-bgqd
-rw-r--r-- 1 root root 37345 Mar 23 15:50
/usr/share/apparmor/cache/d29c4283.0/samba-bgqd


but it *did* update it (see date)

if I stop apparmor, remove /etc/apparmor.d/cache.d/d29c4283.0/samba-bgqd and
restart the cache file size matches
/usr/share/apparmor/cache/d29c4283.0/samba-bgqd and I no longer get the DENIED
for /proc/{pipd}/fd

I will attach a tarball with the data you requested. Let me know if you need
any other info and/or debugging I can do to help