Distrobox, by default, doesn’t provide much isolation/sandboxing - it’s main aim is desktop integration and filesystem transparency. So if you’re trying to use it for isolation, it’s a bad idea.
However, you can create a new container which will isolate your filesystem and prevent such conflicts, using the –unshare-devsys flag. (if you want FULL isolation though, use the –unshare-all flag).
Then enter the container and install the flatpak app as usual.
I just tested this on Fedora uBlue and an Arch container and it works fine, didn’t have to unmount anything.
If you’re after fluid yet lightweight animations then you should definitely check out Wayfire. Yes it’s Wayland and a WM not a DE, but you can get a distro/spin with Wayfire and all the stuff you need for a DE all pre-installed and pre-configured. Wayblue (based on Fedora uBlue) is one such option you can try. And because Wayblue is immutable and has reliable atomic updates, it’d make a great option for you as a school-goer as stuff rarely breaks and you can always rollback to a previous image before the update.
I have the same chip in my mini PC (7840HS) and it works fine for me on Linux, but then again I use Arch + Wayland. Maybe you could try a couple of different distros on a Live USB or something (you could create one using Ventoy and then put a few different ISOs on there to play around with). I’d recommend choosing a distro with a recent kernel and updated graphics stack, for eg Arch or Bazzite and see how it goes.
But the artefacts you describe sound more like a hardware glitch to me. Have you tried running the Lenovo hardware diagnostics from the system boot menu? (IIRC you need to press F12 or something to get the menu and then choose the diagnostics mode).
Completely FOSS isn’t completely self-sustainable either in the real world - you’d need to be using something like RISC-V with coreboot and a completely open hardware stack with zero proprietary firmware blobs in the mix + not to mention running a fully self-hosted email/cloud stack. And if you’re using a mobile phone - even a dumb one or a pinephone - then you’re not fully FOSS. I’m not aware of anyone who’s fully FOSS out there, except maybe RMS?
I use multiple systems and even I feel NixOS is overkill, especially with their confusing and sometimes incomplete documentation.
On the other hand, Nix the package manager has been fantastic - especially if you’re on an immutable OS, or running some ancient “stable” distro - you can get all the packages you want, without breaking your system - and no need to learn the Nix language and write convoluted config files.
We use HP EliteBooks and EliteDesks extensively at work. I even used to set them up in my old job, and as far as I’m aware, it doesn’t connect to the Internet or “phone home” by default (although that could’ve changed in recent models). In any case, one of the nice things about the HP BIOSes is that it’s very configurable - you can disable the automatic BIOS update checks, network adapter etc. I forget if there was an option to just disable the network stack, but what you could do is configure the UEFI network settings so that they’re invalid - ie, set it to a random static IP + random DNS etc (eg: 0.0.0.0) so that it can’t connect even if it tried.
however when I rebase to that image it drops me into rescue mode after reboot. :(
Did you rebase to the unsigned uBlue image first?
rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/startingpoint:latest
This will install the proper signing keys and policies and prepare you to rebase to a different signed image. After you run the above command reboot, and then rebase to the actual image you want to rebase to.
It looks like you’re still using PulseAudio? I’d highly recommend switching to PipeWire+WirePlumber instead, installing it should make your earbuds work automatically.
There are already a few actively maintained forks of Tachiyomi. TachiJ2K and TachiyomiSY are two such popular forks which have several features not present in the original app. In fact, many hardcore manga readers in the community had already switched to them years ago. There’s also Aniyomi, which not only supports manga but also watching anime via extensions, the same way you’d read manga in Tachiyomi.
So thanks to the power of FOSS, Tachiyomi already continues to live on and you don’t need to wait for a fork.
Bazzite. It’s based on Fedora uBlue so it’s technically Fedora, but being an immutable OS, it works quite differently enough that it counts as its own distro. For instance, you don’t use dnf or yum to install stuff, you’d use Flatpak/Distrobox/Nix. Updates are done using the rpm-ostree command, and it’s effectively a rolling release model, but atomic in nature so you get none of the instability that you’d get in a typical rolling release.