Created attachment 583376 [details] /tmp/apparmor-bugreport-p0abeeoy.txt ~> aa-logprof Protokolleinträge von /var/log/messages werden gelesen. AppArmor-Profile in /etc/apparmor.d werden aktualisiert. Traceback (most recent call last): File "/usr/lib/python-exec/python3.6/aa-logprof", line 56, in <module> apparmor.do_logprof_pass(logmark) File "/usr/lib64/python3.6/site-packages/apparmor/aa.py", line 1816, in do_logprof_pass log = log_reader.read_log(logmark) File "/usr/lib64/python3.6/site-packages/apparmor/logparser.py", line 384, in read_log self.add_event_to_tree(event) File "/usr/lib64/python3.6/site-packages/apparmor/logparser.py", line 198, in add_event_to_tree e = self.parse_event_for_tree(e) File "/usr/lib64/python3.6/site-packages/apparmor/logparser.py", line 246, in parse_event_for_tree if profile != 'null-complain-profile' and not self.profile_exists(profile): File "/usr/lib64/python3.6/site-packages/apparmor/logparser.py", line 457, in profile_exists raise AppArmorBug('This should never happen, please open a bugreport!') apparmor.common.AppArmorBug: This should never happen, please open a bugreport! An unexpected error occoured! For details, see /tmp/apparmor-bugreport-p0abeeoy.txt Please consider reporting a bug at https://bugs.launchpad.net/apparmor/ and attach this file. As I have no launchpad account and does not know where to get one from, and from the fact, that this is a gentoo system and not ubuntu, I report the bug here.
Created attachment 583378 [details] emerge --info
Which version of sys-apps/apparmor-utils is installed?
[I] sys-apps/apparmor-utils Verfügbare Versionen: ~2.13.1^t (~)2.13.2^t (~)2.13.2-r1^t {PYTHON_TARGETS="python3_5 python3_6"} Installierte Versionen: 2.13.2-r1^t(17:48:29 05.07.2019)(PYTHON_TARGETS="python3_6 -python3_5") Startseite: https://gitlab.com/apparmor/apparmor/wikis/home Beschreibung: Additional userspace utils to assist with AppArmor profile management
This is possibly fixed in 2.13.3 (https://gitlab.com/apparmor/apparmor/merge_requests/297/diffs). I'll try and bump it soon.
I've bumped 2.13.3 which should contain the fix. Sorry for the delay.