[SOLVED] Error message "Failed to start Load AppArmor profiles" at boot time

no-windose · 05-01-2020, 01:30 PM

I have tried to upgrade Ubuntu from 18.04 bionic to 20.04 focal with the update manager. The process hanged for ever when installing a package called "libgdk-pixbuf" or something similar. So I had to restart the computer. After starting the upgrade process again, this time with the command line "$ apt upgrade", I could not boot. There was an error message:

"Failed to start Load AppArmor profiles."

Could someone please help me to repair the system?

shruggy · 05-02-2020, 06:04 AM

Can you boot into rescue mode or emergency mode? See: https://www.ostechnix.com/how-to-boo...-ubuntu-18-04/

Quote:

Originally Posted by no-windose

I have tried to upgrade Ubuntu from 18.04 bionic to 20.04 focal with the update manager.

From the Ubuntu 20.04 announcement:

Quote:

Users of Ubuntu 19.10 will be offered an automatic upgrade to 20.04 LTS
via Update Manager shortly. Users of 18.04 LTS will be offered the
automatic upgrade when 20.04.1 LTS is released, which is scheduled for
July 23rd.

no-windose · 05-02-2020, 04:15 PM

I can choose "recovery mode" from the GRUB menu. Then the system hangs a bit at "running /scripts/local-premount ...". Then I get the "recovery menu": resume/clean/dpkg/fsck/grub/network/root/system-summary.

shruggy · 05-03-2020, 04:24 AM

Select dpkg.

no-windose · 05-03-2020, 06:53 AM

I have tried already to select dpkg. I have typed:
# dpkg -i libgdk-pixbuf2.0-0
But it makes no difference. I still can't boot.

shruggy · 05-03-2020, 07:30 AM

You misunderstood. Selecting the menu item dpkg in the recovery menu will try to repair broken packages. This is what I mean.

Quote:

Originally Posted by no-windose

# dpkg -i libgdk-pixbuf2.0-0

This command is wrong. The parameter to dpkg -i is supposed to be a .deb file.

no-windose · 05-04-2020, 10:51 AM

Thanks shruggy. I have selected dpkg and the computer has downloaded some stuff which has resulted in a "partial upgrade". But I still can't boot. I get the following message when I try to boot:

A start job is running for /dev/mapper/cryptswap1
Failed to start Load AppArmor profiles.
See 'systemctl status apparmor.service' for details.

no-windose · 05-12-2020, 03:50 PM

It turns out that I had wrongly upgraded from 18.04 to 20.04 on a 32-bit computer. I had changed the /etc/apt/sources.list file to allow the download of 20.04 packages. I should not have done so as 20.04 does not support 32-bit computers.