Waydroid container is brick by the configuration scripts provided by Bazzite ujust on Bazzite 41.

[shawny43]

Describe the bug

Waydroid stop container when session was stopped and brick systemctl to enable or start the container, forced to use the main Waydroid commands to boot container and sessions together. It's happened in fresh install of Bazzite 41 and in fresh configuration of Waydroid. Reset may work but brick when i begining the config section.

Config was on Android 11

• Gapps
• Libndk
• magisk
• fdroidpriv
• widevine

What did you expect to happen?

Waydroid needs to boot the container at startup or even in launch from Waydroid icon on desktop.

Output of rpm-ostree status

State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:7ea28171af3cfeaadd6b07d69feff8d67e97d9a8f070770ae271be8d380612be
                  Version: 41.20241104 (2024-11-04T05:01:16Z)
          LayeredPackages: kvantum openrazer-meta razergenie sassc

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:7ea28171af3cfeaadd6b07d69feff8d67e97d9a8f070770ae271be8d380612be
                  Version: 41.20241104 (2024-11-04T05:01:16Z)
          LayeredPackages: kvantum openrazer-meta razergenie

Hardware

It's a custom AMD Desktop computer.

Extra information or context

Current workaround possible is to boot container and session on terminal individually. Closing terminals actives will close Waydroid.

Also i have to enroll keys for make Bazzite compatible with my secureboot and the UEFI.