@Taz Radxa's u-boot won’t load the kernel image. So I used vmlinux.

This topic is 2 years old and HA formally does not support supervised anymore. And doing 2 such modifications and then hoping all will be fine is false hope IMO. If you don't have a serial console cable to watch kernel en journal log etc to see what your system is doing, maybe it is time now to get one. I have an old supervised inatsllation (not use for many months, but it is plain Debian and a VM so I have free/easy CLI console.

Same here: Installed Home Assistant using armbian-config on a Rock 5b with Armbian Trixie (v26.2.1 for Rock 5B running Armbian Linux 6.18.32-current-rockchip64). I switched from NetworkManager to systemd-networkd. Reboot to enable AppArmor left a system not accessible via ssh after more than 100s. Do we have to wait somewhat longer, or is there currently an issue with the installation of Home Assistant on Armbian Trixie ?

Ok, just wanted to know if you used the flatpak since they indicate on their wiki that could be troublesome. When you say "none of them can start automatically", what methods did you use to configure autostart? As they state at the top of the wiki/setup: "Distribution may provides some specific tool for autostart Fcitx and usually also set up environment variable together." Take notice of the word MAY. Seems Armbian does not. So what does im-config do as described on the next line after that on the wiki page? Does it fail or give you some hints of why autostart is not working? https://fcitx-im.org/wiki/Special:MyLanguage/Setup_Fcitx_5#im-config_(Debian/Debian-based/Ubuntu) This question is more fitting to ask the devs of the application, not the operating system. If you have problems with an application on windows for example, you generally don't ask microsoft for help but rather the developers of the application. But if you provide good enough information, we might be able to help you figure it out on this forum...

none which doesn't break other boards.