Apparmor weird bug: ubports doesn't reboot unless the apparmor cache is deleted.
-
Hello.
I'm trying to port Ubports to Xiaomi Redmi Note 9/Pro/S and I'm encountering a strange bug with AppArmor:
The first boot works fine but after I try to reboot the phone it gets stuck at the Redmi logo and the only way to make it boot is by deleting the
apparmor
folder from/var/cache/
.I've spend 2 days going back and forward and I still haven't found a fix or a reason why this happens.
Did anyone encountered this problem while porting ubports to their device?
Halium branch: halium10
Kernel sources: https://github.com/nitanmarcel/kernel_xiaomi_sm6250
Ubports gitlab repo: https://gitlab.com/nitanmarcel/miatool-haliumThanks!
-
@nitanmarcel Coming with an update about the bug, it's not required to delete the whole folder to boot into in ubports. just the file namedclick_com.ubuntu.ubports_ubports_1.9.1
Edit: False alarm. it looks like it didn't boot this time even after deleting that fileEdit: Again. It booted but after I deleted the folder, booted and then started all over but just by deleting the file
-
After a few days I decided to try another
vendor.img
and out of nowhere reboots worked just fine. I still have no idea why the vendor messed up apparmor but anyway, if someone happens to have the same problem he could try using different vendor images.