Exactly. It handles Jellyfin + other services very well.
Strit
joined 2 years ago
I bought a "cheap chinesium" one a couple of months back and have not regretted it (yet). It does what it claimed it would.
The one I bought: Aoostar R1
I was thinking the same. Could be an IP conflict.
Maybe you where on an older Ubuntu LTS. I don't know which Ubuntu they consider "supported".
I've been running my HA in Docker on Arch Linux for the last 4-5 years and I have never been notified that my OS is unsupported. Could be portainer related.
You didn't mention in your OP that it had to be debian distro packages. I just gave examples of HA being packaged in other ways than a complete OS.
I could have said: "If you want to run HA from packages, you need to install Arch!" But I didn't. Chill out.
It is both.
Home Assistant created an OS for appliance like installations.
But there is also the docker images, repo packages (I know Arch Linux has it in the repo) and pip based packages too.
I have a few things in my Plasma desktop that is not translated. So it seems to be the same as you encounter.
I've just learned to live with it, since it's likely just untranslated strings somewhere.
Shipping prices would vary depending on location though, right?
I know it's active, but most of the stuff being added is not something I use. "Plain old" is a figure of speech for something that is pretty "vanilla".
mlt was also updated, have you tried downgrading that?
Some stuff in your output relates to mlt.
Why not just log in as the user in TTY and then start it?
I'n not sure I understand the use-case of why it needs a Plasma session to start a script that needs to keep running afterwards. If the script itself does not need a plasma session, then you can just start it as a user service with systemd.