<div dir="ltr"><div dir="ltr">Hi,</div><div><br></div><div>please read below.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Sep 3, 2021 at 10:15 AM intrigeri <<a href="mailto:intrigeri@debian.org">intrigeri@debian.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
Ďoďo (2021-09-03):<br>
> Yesterday I noticed that some autoupgrade fully updated my TP. So I removed<br>
> testing, run dist-upgrade to current stable. (TP completely freeze<br>
> during the systemd upgrade) Then I rebooted and exactly the same problem. I<br>
> finished the upgrade (due to previous crash) and again. But the same<br>
> problem.<br>
> So I had downgrade libappramor1 again to be able to boot. :(<br>
<br>
In the original bug report I see this:<br>
<br>
 - "Init: unable to detect"<br>
<br>
 - "The last message before kernel crash was: /sbin/init can not find  apparmor_2.13"<br></blockquote><div><br></div><div>The error message before the /sbin/init crash is the same. </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
So I'm wondering:<br>
<br>
1. What init system are you using?<br></blockquote><div>systemd :( </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
   Please share the output of this command:<br>
<br>
     dpkg -S /sbin/init<br></blockquote><div> systemd-sysv: /sbin/init</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
2. What's the currently installed version of libc6?<br>
<br>
   Please share the output of this command:<br>
<br>
     apt policy libc6<br></blockquote><div> libc6:</div>  Installed: 2.31-17<br>  Candidate: 2.31-17<br>  Version table:<br> *** 2.31-17 100<br>        100 /var/lib/dpkg/status<br>     2.31-13 500<br>        500 <a href="http://ftp2.de.debian.org/debian">http://ftp2.de.debian.org/debian</a> stable/main amd64 Packages<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
3. What version of apparmor is installed when the bug happens?<br></blockquote><div>2.13.6 </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
   Please share the output of this command:<br>
<br>
     apt policy apparmor libapparmor1<br></blockquote><div> apt policy apparmor libapparmor1</div>apparmor:<br>  Installed: 2.13.6-10<br>  Candidate: 2.13.6-10<br>  Version table:<br> *** 2.13.6-10 500<br>        500 <a href="http://ftp2.de.debian.org/debian">http://ftp2.de.debian.org/debian</a> stable/main amd64 Packages<br>        100 /var/lib/dpkg/status<br>libapparmor1:<br>  Installed: 2.13.6-10<br>  Candidate: 2.13.6-10<br>  Version table:<br> *** 2.13.6-10 500<br>        500 <a href="http://ftp2.de.debian.org/debian">http://ftp2.de.debian.org/debian</a> stable/main amd64 Packages<br>        100 /var/lib/dpkg/status<br><br>Hm, it was again automaticaly upgraded since yesterday. I need to have 2.13.2 to boot: </div><div class="gmail_quote">Already prepared: root@opahapaka:~# ls libapparmor1_2.13.2-10_amd64.deb</div><div class="gmail_quote">Making system bootable again:</div><div class="gmail_quote">dpkg -i !$<br>dpkg -i libapparmor1_2.13.2-10_amd64.deb<br>dpkg: warning: downgrading libapparmor1:amd64 from 2.13.6-10 to 2.13.2-10<br>(Reading database ... 392196 files and directories currently installed.)<br>Preparing to unpack libapparmor1_2.13.2-10_amd64.deb ...<br>Unpacking libapparmor1:amd64 (2.13.2-10) over (2.13.6-10) ...<br>Setting up libapparmor1:amd64 (2.13.2-10) ...<br>Processing triggers for libc-bin (2.31-17) ...<br><br>Thanks for you help</div><div class="gmail_quote"><br></div><div class="gmail_quote">Jozef<br><div> </div></div></div>