UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Apparmor weird bug: ubports doesn't reboot unless the apparmor cache is deleted.

    Scheduled Pinned Locked Moved Porting
    3 Posts 1 Posters 859 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
      Reply
      • Reply as topic
      Log in to reply
      This topic has been deleted. Only users with topic management privileges can see it.
      • N Offline
        nitanmarcel
        last edited by

        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-halium

        Thanks!

        N 1 Reply Last reply Reply Quote 0
        • N Offline
          nitanmarcel @nitanmarcel
          last edited by nitanmarcel

          @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 named click_com.ubuntu.ubports_ubports_1.9.1

          Edit: False alarm. it looks like it didn't boot this time even after deleting that file

          Edit: Again. It booted but after I deleted the folder, booted and then started all over but just by deleting the file

          1 Reply Last reply Reply Quote 0
          • N Offline
            nitanmarcel
            last edited by

            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.

            1 Reply Last reply Reply Quote 1

            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

            With your input, this post could be even better 💗

            Register Login
            • First post
              Last post