Hello asdasda and thanks for this bug report. You are right: in Jammy there is a discrepancy between the samba-bgqd path and its path in the samba-bgqd apparmor profile (from apparmor-profiles). This issue is not present in Kinetic as samba-bgqd has been moved under /usr/libexec, see the following changelog entry:
* move helper programs from /usr/lib/$multiarch/ to /usr/libexec/
where they belongs. This should not affect users.
While it's tempting to backport this change, from the SRU point of view it's probably more appropriate to fix the path in the apparmor profile, so I'm adding an apparmor task to this bug.
Hello asdasda and thanks for this bug report. You are right: in Jammy there is a discrepancy between the samba-bgqd path and its path in the samba-bgqd apparmor profile (from apparmor-profiles). This issue is not present in Kinetic as samba-bgqd has been moved under /usr/libexec, see the following changelog entry:
samba (2:4.16.0+dfsg-1) experimental; urgency=medium
* move helper programs from /usr/lib/ $multiarch/ to /usr/libexec/
where they belongs. This should not affect users.
While it's tempting to backport this change, from the SRU point of view it's probably more appropriate to fix the path in the apparmor profile, so I'm adding an apparmor task to this bug.