Andreas:
Thanks for the prompt reply your suggestion has fixed the problem. The only 
thing to note is that after the reinstall the following appeared on dmesg

[693175.025594] kauditd_printk_skb: 29 callbacks suppressed
[693175.025596] audit: type=1400 audit(1744704729.950:1332): apparmor="STATUS" 
operation="profile_replace" info="same as current profile, skipping" 
profile="unconfined" name="ubuntu_pro_apt_news" pid=121719 
comm="apparmor_parser"
[693175.224630] audit: type=1400 audit(1744704730.149:1333): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="ubuntu_pro_esm_cache" 
pid=121722 comm="apparmor_parser"
[693175.235162] audit: type=1400 audit(1744704730.159:1334): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="ubuntu_pro_esm_cache//apt_methods" pid=121722 comm="apparmor_parser"
[693175.236055] audit: type=1400 audit(1744704730.160:1335): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="ubuntu_pro_esm_cache//apt_methods_gpgv" pid=121722 comm="apparmor_parser"
[693175.237143] audit: type=1400 audit(1744704730.161:1336): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="ubuntu_pro_esm_cache//cloud_id" pid=121722 comm="apparmor_parser"
[693175.237705] audit: type=1400 audit(1744704730.162:1337): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="ubuntu_pro_esm_cache//dpkg" pid=121722 comm="apparmor_parser"
[693175.238482] audit: type=1400 audit(1744704730.163:1338): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="ubuntu_pro_esm_cache//ps" pid=121722 comm="apparmor_parser"
[693175.238911] audit: type=1400 audit(1744704730.163:1339): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="ubuntu_pro_esm_cache//ubuntu_distro_info" pid=121722 
comm="apparmor_parser"
[693175.239485] audit: type=1400 audit(1744704730.164:1340): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="ubuntu_pro_esm_cache_systemctl" pid=121722 comm="apparmor_parser"
[693175.239932] audit: type=1400 audit(1744704730.164:1341): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="ubuntu_pro_esm_cache_systemd_detect_virt" pid=121722 
comm="apparmor_parser"

but running "systemctl restart apt-news.service" no longer results in
any more messages being printed.

Does this mean that the problem wasn't a real issue? The machine this
happened on was freshly installed on the 4th April 2025. However looking
through /var/log/apt/history.log says the ubuntu-pro-client package was
originally installed as part of a transaction from "Start-Date:
2025-02-16  21:00:10 / End-Date: 2025-02-16  21:00:28" which pre-dates
the machine's actual install!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2107332

Title:
  AppArmor denied audit messages related to __pycache__ in dmesg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2107332/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to