If i look in var/log/boot.log after a forcefsck, the system have a description of hard disk like : /dev/sda1 : 1627009/3571712 fichiers (0.3% non-contigus), 6708217/14284032 blocs. It seems to be ok for the check disk during boot, no?
So, when plymouth loops without end, press "esc" and then press "right arrow", i have seen a brief message "skip apparmor" before the "re"start of the boot.
I have tested with a live usb session.
sudo fsck /dev/sda1 (my boot partition).
Result : clean.
If i look in var/log/boot.log after a forcefsck, the system have a description of hard disk like : /dev/sda1 : 1627009/3571712 fichiers (0.3% non-contigus), 6708217/14284032 blocs. It seems to be ok for the check disk during boot, no?
So, when plymouth loops without end, press "esc" and then press "right arrow", i have seen a brief message "skip apparmor" before the "re"start of the boot.
Apparmor should have link with the problem?