[pkg-apparmor] Bug#983114: libapparmor1: After upgrade is the system not bootable. Init is complaining about incorrect apparmor version.

[Ďoďo]

Hi,

please read below.

On Fri, Sep 3, 2021 at 10:15 AM intrigeri <intrigeri at debian.org> wrote:

> Hi,
>
> Ďoďo (2021-09-03):
> > Yesterday I noticed that some autoupgrade fully updated my TP. So I
> removed
> > testing, run dist-upgrade to current stable. (TP completely freeze
> > during the systemd upgrade) Then I rebooted and exactly the same
> problem. I
> > finished the upgrade (due to previous crash) and again. But the same
> > problem.
> > So I had downgrade libappramor1 again to be able to boot. :(
>
> In the original bug report I see this:
>
>  - "Init: unable to detect"
>
>  - "The last message before kernel crash was: /sbin/init can not find
> apparmor_2.13"
>

The error message before the /sbin/init crash is the same.

>
> So I'm wondering:
>
> 1. What init system are you using?
>
systemd :(

>
>    Please share the output of this command:
>
>      dpkg -S /sbin/init
>
 systemd-sysv: /sbin/init

>
> 2. What's the currently installed version of libc6?
>
>    Please share the output of this command:
>
>      apt policy libc6
>
 libc6:
  Installed: 2.31-17
  Candidate: 2.31-17
  Version table:
 *** 2.31-17 100
        100 /var/lib/dpkg/status
     2.31-13 500
        500 http://ftp2.de.debian.org/debian stable/main amd64 Packages

>
> 3. What version of apparmor is installed when the bug happens?
>
2.13.6

>
>    Please share the output of this command:
>
>      apt policy apparmor libapparmor1
>
 apt policy apparmor libapparmor1
apparmor:
  Installed: 2.13.6-10
  Candidate: 2.13.6-10
  Version table:
 *** 2.13.6-10 500
        500 http://ftp2.de.debian.org/debian stable/main amd64 Packages
        100 /var/lib/dpkg/status
libapparmor1:
  Installed: 2.13.6-10
  Candidate: 2.13.6-10
  Version table:
 *** 2.13.6-10 500
        500 http://ftp2.de.debian.org/debian stable/main amd64 Packages
        100 /var/lib/dpkg/status

Hm, it was again automaticaly upgraded since yesterday. I need to have
2.13.2 to boot:
Already prepared: root at opahapaka:~# ls libapparmor1_2.13.2-10_amd64.deb
Making system bootable again:
dpkg -i !$
dpkg -i libapparmor1_2.13.2-10_amd64.deb
dpkg: warning: downgrading libapparmor1:amd64 from 2.13.6-10 to 2.13.2-10
(Reading database ... 392196 files and directories currently installed.)
Preparing to unpack libapparmor1_2.13.2-10_amd64.deb ...
Unpacking libapparmor1:amd64 (2.13.2-10) over (2.13.6-10) ...
Setting up libapparmor1:amd64 (2.13.2-10) ...
Processing triggers for libc-bin (2.31-17) ...

Thanks for you help

Jozef
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-apparmor-team/attachments/20210903/a07ca366/attachment.htm>