If you’re an Ubuntu 18.04 user and you’ve encountered a boot hang issue with the message “A start job is running for AppArmor initialization”, you’re not alone. This problem can be frustrating, but fortunately, there are ways to fix it. In this article, we’ll guide you through the process step by step.
To fix the issue of Ubuntu 18.04 boot hangs indefinitely on "Start Job for AppArmor Initialization", you can access the GRUB boot menu, enter recovery mode, drop to the root shell prompt, disable the AppArmor service, and reboot your system. Alternatively, you can try adding the "systemd.mask=apparmor.service" option in the GRUB boot options.
Understanding the Issue
Before we delve into the solution, it’s important to understand the problem. AppArmor is a Linux kernel security module that allows the system administrator to restrict programs’ capabilities with per-program profiles. Sometimes, due to various reasons like system updates, configuration changes, or software conflicts, the AppArmor service might cause the system to hang during boot.
Accessing the GRUB Boot Menu
The first step to resolve this issue is to access the GRUB boot menu. To do this:
- Reboot your machine.
- Hold the
Shiftkey as soon as you pass the BIOS logo. This should bring up the GRUB boot menu.
Entering Recovery Mode
Once you’re in the GRUB boot menu:
- Select “advanced options” and hit
- Select the option with “(recovery mode)” in front of it and hit
You should now be in recovery mode.
Dropping to Root Shell Prompt
In recovery mode:
- Wait until the machine boots and another menu appears.
- Choose the option with “drop to root shell prompt” and hit
Enterwhen it says “press Enter for maintenance.”
You should now be at the command prompt.
Disabling the AppArmor Service
At the command prompt:
- Enter the following command to give read and write access to your system:
mount -o rw,remount /
mountcommand is used to mount filesystems. The
-ooption allows you to specify several system options. In this case,
rwstands for read-write and
remounttells the system to remount the filesystem.
- Disable the AppArmor service by entering the following command:
sudo systemctl disable apparmor.service
systemctlcommand is used to control the systemd system and service manager.
disableis an option that prevents the service from starting at boot.
- Reboot your system.
If everything goes as planned, your system should now boot normally.
If you’re unable to access recovery mode due to the same issue, you can try an alternative method:
- At the GRUB menu, press “e” to edit the boot options.
- Move the cursor after the last character in the last options line and press
Enterto start a new line.
- Add “systemd.mask=apparmor.service” with no spaces and then press
F10to boot the system.
systemd.mask= option is a way to prevent a service from starting, similar to the
disable option in
Once your system is back to normal, you can enable the AppArmor service again for security purposes. To do this, run the following command in the terminal:
sudo systemctl enable apparmor.service
This command will enable the AppArmor service to start at boot.
While boot hang issues can be frustrating, they are often solvable with a bit of patience and the right steps. We hope this guide has helped you resolve the “A start job is running for AppArmor initialization” issue on Ubuntu 18.04. If you’re still experiencing problems, don’t hesitate to seek help from Ubuntu’s community forums.
AppArmor is a Linux kernel security module that allows the system administrator to restrict programs’ capabilities with per-program profiles.
Sometimes, due to various reasons like system updates, configuration changes, or software conflicts, the AppArmor service might cause the system to hang during boot.
To access the GRUB boot menu, reboot your machine and hold the
Shift key as soon as you pass the BIOS logo. This should bring up the GRUB boot menu.
In the GRUB boot menu, select "advanced options" and hit
Enter. Then, select the option with "(recovery mode)" in front of it and hit
To disable the AppArmor service, follow the steps mentioned in the article. Enter the command
sudo systemctl disable apparmor.service while in the root shell prompt of recovery mode.
If you’re unable to access recovery mode, you can try an alternative method. At the GRUB menu, press "e" to edit the boot options, add "systemd.mask=apparmor.service" with no spaces, and then press
F10 to boot the system.
Once your system is back to normal, you can enable the AppArmor service again by running the command
sudo systemctl enable apparmor.service in the terminal.
If you’re still experiencing problems, don’t hesitate to seek help from Ubuntu’s community forums at [https://ubuntuforums.org/].