I’ve found that as well with some files. At first I thought the issue was with the jellyfin instance had not enough capabilities, but after trying the same file with its subtitles, it worked on any other client: flatpak, web, and regular android. So for me it is the chromecast/androidtv device, so I am now looking what to replace it with
Firefox, with ublock origin and yt high definition plugins, so I can have a decent yt player. I have disabled/hide chrome, I have no need for it.
What are you reinstalling? New haos on old kvm? Old haos on new kvm? New deployment?
From the logs I read that your user chris has no rw perms within the haos.
I’m not sure if your issue is narcisism or bestiality
I somehow missed this to be a flatpak via Discover. Granted this may not be usual in distros with a traditional update model, downgrading packages may be present in rolling distros, or distros with overlapping minor versions, or having 3rd party repos providing conflicting packages to those of the distro.
I offer my system as example:
The following product is going to be upgraded:
openSUSE Tumbleweed 20240211-0 -> 20240313-0
The following 14 packages are going to be downgraded:
ghc-binary ghc-containers ghc-deepseq ghc-directory ghc-exceptions ghc-mtl ghc-parsec ghc-pretty ghc-process ghc-stm ghc-template-haskell ghc-text ghc-time ghc-transformers
It is called “downgrading”, and it is not uncommon to have some packages downgrading when updating/upgrading a system, due to several reasons.
Just take into consideration that battery powered zigbee devices most likely won’t act as repeater/router, for that you may need a wall plugged device.
And yes, the few non-tasmota flashed wifi devices I have ping home a lot
You know landlines are still in use, right?
That is why I also mentioned the latch/sensor, it may got stuck.
It sounds like the issue is with the lid latch/sensor, not with the graphics. Some laptops may not boot if the lid is closed, and some have options on the firmware to enable to boot when the lid is closed / on a docking station.
With vbox I don’t think you can do that, nor with any other hypervisor delivering full virtualization. You could try with a paravirtualization, like Xen, and see if you can trick the OS
Note that I don’t know if windows is supported as a paravirtualized guest.
Disabling it at bios level does not suit your case?