Hi,
Regarding the specific buggy case you've met: Christian asked you some
more info in https://bugs.debian.org/805145#10. Any chance you
provide it?
Regarding how widespread the triggers that bug are: since 2.10.95-2
the snippets included by dh-apparmor in postinst use aa-enabled (which
is a
Hi Patrick,
Christian Boltz wrote (15 Nov 2015 16:08:35 GMT) :
> Please provide the output of
> wc -l /sys/kernel/security/apparmor/profiles
> time aa-status # be patient, please ;-)
> [...]
> BTW: Do you really have a profile for /usr/bin/python2.7? That's probably
> a bad idea ;-)
Package: apparmor
Version: 2.10-2+b1
Severity: important
File: /usr/sbin/aa-status
Dear Maintainer,
upgrading packages which includes apparmor profiles and execute aa-status
during the upgrade process leads to indefinitely running aa-status process.
Only a kill -9 on the process helps to finish
Hello,
the crash log contains a very interesting detail - you killed aa-status
while it worked on the profile
/usr/bin/python2.7//null-5ec//null-5ed//null-5...5ef//null-667//null-668//null-574fe
(the line was shortened when python created the crash log, there were
probably more null-*
4 matches
Mail list logo
