Hello, Am Dienstag, 29. Oktober 2019, 06:29:49 CET schrieb Jacek: > sys-apps/apparmor-utils-2.13.3
I had some hope that 2.13.3 has this already fixed ;-) This makes my remaining question more important - can you please provide the log messages that trigger this bug? grep chrome /var/log/audit/audit.log | grep trace Note that the log filename might differ - if you don't have auditd running, it could also be /var/log/messages or /var/log/syslog. (To make things easier - aa-logprof prints the logfile it uses on startup.) > >> /usr/lib64/python3.6/site-packages/apparmor/rule/__init__.py in > >> is_covered(self=<PtraceRule> ptrace read > >> peer=/opt/google/\*/chrome,, > >> other_rule=<PtraceRule> ptrace read peer=chrome,, > >> check_allow_deny=False, check_audit=False) Regards, Christian Boltz -- > openSUSE [...] is a project driven by "Those who do, decide" This is bullshit, sorry. Because "Those who undo, decide too". [> Richard Brown and Stephan Kulow in opensuse-project]
signature.asc
Description: This is a digitally signed message part.
-- AppArmor mailing list AppArmor@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/apparmor