enterprise-support team mailing list archive

[Paride Legovini <1979879@xxxxxxxxxxxxxxxxxx>]

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.

** Changed in: samba (Ubuntu)
       Status: New => Triaged

** Also affects: apparmor (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: apparmor (Ubuntu)
       Status: New => Triaged

** Tags added: server-todo

-- 
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to samba in Ubuntu.
Matching subscriptions: Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/1979879

Title:
  Apparmor profile in 22.04 jammy - fails to start when printing enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1979879/+subscriptions