[pkg-apparmor] Bug#884278: prevent deinstallation of boot-critical package

Vincas Dargis vindrg at gmail.com
Thu Dec 14 18:33:41 UTC 2017


On 2017-12-14 19:21, Joachim Wuttke wrote:
>> Could you check what packages on your system have installed have shipped
>> AppArmor profile, and so maybe causing the issue, like this:
>>
>> dpkg -S /etc/apparmor.d/
> 
> # dpkg -S /etc/apparmor.d/
> apparmor-profiles-extra, apparmor: /etc/apparmor.d
> 

Thanks, though sadly it does not give a hint.

Wouldn't it be too harsh to ask you to try that again, i.e. removing apparmor
packages, but this time, without "quiet" kernel parameter?

It could be done by editing `/etc/default/grub` file, removing "quiet" in
this line:

GRUB_CMDLINE_LINUX_DEFAULT="quiet"

After that, `sudo update-grub` and reboot.

If that reproduces, maybe this time it would give more info upon crash or
any other kind of malfunction.

Also, maybe `/var/log/kern.log` or `/var/log/kern.log.X.gz` files has
some more hints?



More information about the pkg-apparmor-team mailing list